Histórico da Página
Purpose
The procedure of Budgetary Contingency Release - PCO aims at controlling the requests of contingencies from a workflow through Fluig.
Requirements
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 |
Premises
- To have Fluig environment connected to Protheus
- To have registered user
Benefits
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.
...
Deck of Cards | |||||
---|---|---|---|---|---|
| |||||
|
Process Activities
Activity: Request Budgetary Contingency
...
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
...
Instruction: Accessing Fluig with contingency approver login generating a new task for it.
Activity: Approved and Rejected via Fluig
...
Instruction: Access the blocked process and edit the status, indicating the approval and rejection.
Activity: Register Approval/Rejection
...
Instruction: Save the contingency release to send return to Protheus.
Activity: Return Approval/Rejection
...
Instruction: Access Protheus to check the Budgetary Contingency Release status. With contingency released, the request move is run.
How to use
Starting the Process by Protheus
Deck of Cards | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
...
Moving and Querying the Process by Fluig
Deck of Cards | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||
|
Finishing the Process by Protheus
...
Deck of Cards | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||
|
How to Integrate
Query procedures to Release Processes in Protheus and Configure Processes in Fluig through the link: Creating a new Workflow in Protheus.
Considerations
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.
...
For further information on Fluig x Protheus integration, query: Fluig Framework.