The procedure of Budgetary Contingency Release - PCO aims at controlling the requests of contingencies from a workflow through Fluig.
Configure the following parameter:
Name | MV_PCOWFCT |
Type | Numeric |
Cont. Port | 2 |
Description | Indicates whether the workflow for budgetary contingency release - PCO is generated 0 - Workflow disabled 1 - Only e-mail delivery 2 - Workflow through Fluig |
Enables the approval process of actions run in the Budgetary Contingency Release - PCO is execute in a simpler and faster way, and it can be executed directly on Fluig interface, together with other daily processes in an integrated manner.
Business Environment
Segment
Services
Business Areas
Budgetary Planning and Control
Workflow Processes
Process Activities
Activity: Request Budgetary Contingency
Description: Budgetary block against configuration
Instruction: When reaching the block point, you will know the reason of the block. You can request a contingency for the approver.
Activity: Send Workflow via Fluig
Description: The workflow is sent to Fluig.
Instruction: Accessing Fluig with contingency approver login generating a new task for it.
Activity: Approved and Rejected via Fluig
Description: Defines if contingency is approved by Fluig.
Instruction: Access the blocked process and edit the status, indicating the approval and rejection.
Activity: Register Approval/Rejection
Description: After editing the field Status, the edition must be saved.
Instruction: Save the contingency release to send return to Protheus.
Activity: Return Approval/Rejection
Description: The answer is sent to Protheus and the request is moved to Fluig. If not approved, the Budgetary Contingency Release remains blocked in Protheus and can be unblocked by the system (or the block may be kept)
Instruction: Access Protheus to check the Budgetary Contingency Release status. With contingency released, the request move is run.
Starting the Process by Protheus
|
|
|
Query procedures to Release Processes in Protheus and Configure Processes in Fluig through the link: Creating a new Workflow in Protheus.
We inform that is highly important to have technical expertise to deployed the component at Fluig. If you need, we suggest the purchase of consultancy hours to help you Deploy these components in TOTVS channel serving you or through Fluig Store.
All traded and distributed products in Fluig Store have Fluig Store platform as requirements for working.
For further information on Fluig x Protheus integration, query: Fluig Framework.