Skip to main content
Solved

PSO / FSM - Assign Based on Work Status


jbernardo
Hero (Partner)
Forum|alt.badge.img+13

In FSM, mobile users have an "On shift" & "Off shift" option. This is located under PERSON.WORK_STATUS.
Is it possible to have PSO schedule a tech only when they're ON SHIFT and when they are OFF SHIFT it does not consider them for work?

Thanks in advance,

Best answer by Abrar khan

@jbernardo  Assuming you are talking about job Scheduling and not job commitment (sending to the mobile device) this functionality works based on the calendar definition and not on the work status. looks like there is a very specific case you are trying to address i.e when the tech did not go “on shift” and his working hours have started and a new job has been sent for scheduling. 

In PSO you will need to use the exception “Failed To Logon” to notify of such a situation and handle it via a creating a non-availability for the duration if the tech is sick or unavailable.

View original
Did this topic help you find an answer to your question?

6 replies

Forum|alt.badge.img+5
  • Sidekick (Employee)
  • 6 replies
  • Answer
  • August 6, 2020

@jbernardo  Assuming you are talking about job Scheduling and not job commitment (sending to the mobile device) this functionality works based on the calendar definition and not on the work status. looks like there is a very specific case you are trying to address i.e when the tech did not go “on shift” and his working hours have started and a new job has been sent for scheduling. 

In PSO you will need to use the exception “Failed To Logon” to notify of such a situation and handle it via a creating a non-availability for the duration if the tech is sick or unavailable.


jbernardo
Hero (Partner)
Forum|alt.badge.img+13
  • Author
  • Hero (Partner)
  • 171 replies
  • August 7, 2020

Thank you @Abrar khan 


  • Superhero (Employee)
  • 1426 replies
  • August 9, 2020

If you’re using the SDS to automatically commit work you could use the rule “LogonRequired” to only commit to resources that actually log on.  


jbernardo
Hero (Partner)
Forum|alt.badge.img+13
  • Author
  • Hero (Partner)
  • 171 replies
  • August 10, 2020
anmise wrote:

If you’re using the SDS to automatically commit work you could use the rule “LogonRequired” to only commit to resources that actually log on.  

@anmise  are you referring to the scheduling app param in FSM called LOGON_REQUIRED? (If Y, activities may only be committed to resources that are logged on. )

We have it set to Y but it still gets committed.


  • Superhero (Employee)
  • 1426 replies
  • August 11, 2020
jbernardo wrote:
anmise wrote:

If you’re using the SDS to automatically commit work you could use the rule “LogonRequired” to only commit to resources that actually log on.  

@anmise  are you referring to the scheduling app param in FSM called LOGON_REQUIRED? (If Y, activities may only be committed to resources that are logged on. )

We have it set to Y but it still gets committed.

I’m talking about the rules in the resource workspace in PSO. This is where you define how the SDS should behave. The rules/rule collection is then assigned to resources/resource groups. I cannot remember off the top of my head if there’s a scheduling app param you need to set in FSM to use the SDS.

 

 


jbernardo
Hero (Partner)
Forum|alt.badge.img+13
  • Author
  • Hero (Partner)
  • 171 replies
  • August 11, 2020

Oh sorry, no were not using SDS, this is the way our PSO workbench looks like

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings