FastTrack360 Version 12 Online Help
Business Process Management Engine (BPME)
- Fiona Sims
The FastTrack 360 system comes with an inherent business process workflow, however each business will have their own specific process requirements.
The BPME (Business Process Management Engine) tool provides the ability to enforce and configure additional processes within the application.
Additional controls and rules can be applied at the following hierarchy levels:
Global - where rule(s) are applied to fields within a primary record:
Parent
Client
Cost Centre
Contact
Job Order
Candidate
Parent - where rule(s) are applied to fields belonging to a specific Parent's Client records OR Job Order records.
Client - where rule(s) are applied to fields belonging to a specific Client's Job records.
The following limitations can be used to enforce field requirements:
Mandatory - make a field mandatory to be completed, the user will not be able to save the record without the field being completed.
Field Value - customise the expected value for a field by setting limitations on the scope of information that can be applied, for example the value entered must be between 1 and 5.
Masks - used for formatting requirements for a field item, for example where a field needs to be an exact number of digits a mask can be applied to prevent the user from entering data that does not comply with the format.
Please be aware that there is a technical limitation where Masking cannot be applied when creating a new job for the following BPME rule types:
Client > Job Order
Parent > Job Order
Job Order with Client Name filter
Filters can be applied to rules, where a rule item is only required to run when certain conditions within a record have been met. For example, where the rule is that the 'Industry' field in the Parent record is mandatory, however only where the Parent Record's 'Status' is equal to 'Active', a filter condition is applied to assign the status requirement.
Multiple Field Rules can be created within a BPME rule where more than one field condition applies to the rule requirements.
Please be aware that a BPME rule is specific to events that occur where a user is clicking on an action within the page (entity) the rule is defined for - so where a change to the entity is instigated via another function / process, the page BPME rule will not be executed as there is no edit via the screen and click on an action to trigger the rule.
An example of this would be if a custom BPME rule created for the Candidate record that where a user clicks Save, check for certain fields are populated where a user tries to change the status to a particular value. A Candidate’s status can also be automatically updated via Referral Workflow stage move, where that stage has a ‘Candidate Status’ defined. In this circumstance as the status change is being executed by a background worker from a different area of the product, the BPME rule will not be triggered.
Click on any of the Child Pages below to navigate to the help topic you want to view. Alternatively, use the table of contents on the left-hand side to navigate to a topic.
Â
Â
Related pages
Classification-Public