inFlowTracerPro
| The state of the art tool for documenting, tracking and efficiently managing all kinds of information within a company (topics), such as tasks, performances, questions, enhancement suggestions, change requests, services, helpdesk or support tickets and problem reports (during all phases of the development of software applications). The inFlowTracerPro application allows to know on what and how persons work in a company. It can be completed with another Pulsar tool, iActivityTracer, allowing to know why, when and where persons are present or not (tracking and allowance of holidays, illness, training, consultancy, etc.). |
Please find the full application here (restricted access).
|
Application ScopeThe inFlowTracer project includes:
|
TechnologyThis application was built using Pulsar's framework called GID/GIDPro. GIDPro is initially an assembly of several top market open source libraries forming together a consistent development and runtime platform.This framework allows rapid application development (RAD) of Web applications being coupled with relational databases. in an extensible, modular and reliable architecture. It includes a wizard and a repository for registering easily all page items, actions and navigation links. Other standard technologies used in the development of this application are:
|
Main ConceptsTOPICSTopics are information having a life-cycle along a list of users. They are linked to specific applications/projects which hierarchy appears in a tree. Each topic follows a specific template that defines its look and status flow. TEMPLATES Each topic follows a specific template that defines its look and status flow:
|
![]() |
| STATUS FLOW A status flow restricts the list of status a topic can take. It also defines which role can move a topic from which status to which other one. Here aside, an example of a status flow for bug reports. USER ROLES (PROFILES) Users are assigned a role within an application/project and for a specific template, which defines which actions are allowed to them.
|
![]() |
| The general diagram given below shows the life-cycle of information stored into each template all along the phases of project management, as well as the correspondences between templates. |
![]() |
![]() |
Menu An application or project may be selected in the combo box of the menu frame, on the left part of the screen. The current template must always be selected in the 2nd combo box of the menu frame. An application part or subproject may be selected by clicking in the tree displayed in the menu frame, on the left part of the screen. The button Unselect allows to undo the selection made in the tree. A preferred tree can be displayed with only the branches predefined by the user. Search It is possible to search topics either using predefined search criteria or using a query.
![]() |
Using queries is recommended specifically for:
|
![]() |
|
Remark: all print actions generate a report in pdf format.![]() |
The following actions are available on topics:
|
![]() |
Administration ScreensAny person with a role of QA Officer for a combination of application and template has user admin rights for that particular combination. The user admin has the right to modify an existing project structure or to add a new application/project. He can also import/export a structure via XML.The user admin must take care of the information versioning by associating version and phase labels to a project at appropriate time. |
![]() |
| History of changes made to an application can be recorded for each version. The user admin can see who is assigned which role for a specific combination of application and template. He can grant new roles or revoke existing ones. |




inFlowTracerPro







