committed activities are uncommitting after some time

Hi ​@etmshiy 

It depends on the commit rule setup you are using.

For example, the PSO DSP service can suggest uncommitting an activity even after it has been manually committed, due to a resource logoff scenario. When a dispatcher manually commits an activity (status 30+), it is fixed to the resource. However, if the resource is not logged on or later logs off or triggers the LogoffUncommit rule, the DSP may determine that the resource is no longer operationally available.

In this case, the DSP will suggest the external application (in the case IFS Cloud) setting the activity back to uncommitted (status 0). If the external application acknowledges the suggestion, this overrides the manual commitment because the resource’s availability status takes precedence over the dispatcher’s manual assignment.

In short, a manual commit can be undone by the DSP if a subsequent resource status change (such as logoff) activates the LogoffUncommit rule.

This is just one possible scenario. Without reviewing the commit rule set and the underlying data, it’s difficult to determine the exact cause.

Thanks for sharing this information, is it possible to overide this issues when he is offline , because normally in FSM & PSO we can commit irrespective of Resources loged in of logged off.

Where can i check this Commit rule in Cloud.

Regards,

etmshiy

Hi ​@etmshiy 

Activities can be manually committed regardless of whether the resource is logged on or off as you said. However, in scenarios like the one described earlier, PSO may subsequently suggest uncommitting those activities. This is expected behavior. PSO only issues a suggestion based on the configured rules; it is the responsibility of the integration layer (IFS Cloud or FSM) to acknowledge and handle that suggestion appropriately.

I believe in an IFS Cloud–PSO integration, the rules and rule parameters are maintained entirely within PSO, organized under a Rule Collection. From the IFS Cloud side, we simply map the relevant Rule Collection to the scheduling resources or scheduling resource types during the Scheduling basic data setup.

To review or validate the rule and parameter configuration, navigate in the PSO application to:
Planning → General Data → Rules, then select the relevant dataset to view the associated rules and their parameters.

Also, If you don't mind you can attach the scheduling load XML file with the example activity ID & Resource ID and to have a closer look. 

Hi, I can able to commit the job but its not passing to mobile in IFS cloud, do i need to manually transfer from IFS cloud or is there any way i can directly pass from PSO to IFS Cloud Mobile application.

Regards.

etmshiy