Field Service

Get Involved. Join the Conversation.

Topic

    keerthi P
    Is_activity_scheduled in block conditions
    Topic posted October 15, 2017 by keerthi PSilver Medal: 2,000+ Points 
    82 Views, 3 Comments
    Title:
    Is_activity_scheduled in block conditions
    Content:

    Hi,

    We have a requirement to change the activity status when an activity is scheduled. For this, we created a custom status field and implemented set property on activity status. However, this is not working as expected. Below are the observations:

    1. When an activity is scheduled, messages shows that delivered(inserted). However, we see the activity as still old status.

    Can somebody explains how exactly is_activity_scheduled block condition works?

    In the same way, is there a way to identify when an activity changes to unscheduled from scheduled?

    Thank you

    Version:
    OFSC 17.2

    Comment

     

    • Hardik Gupta

      Hi Keerthi,

      I guess you are talking about moving the activity from "Non-Scheduled" queue to a "scheduled" queue(assigning a date).

      So the Launch Condition will be "Move activity".

      Step 1 : Create a Msg Scenario with Move Activity as Launch Condition.

      Step 2: Create a new message step. Select Delivery channel as Set Property. In message patterns add the field in subject and the value to be updated in Body.

      I assume you have done the above steps.

      Step 3: Add the blocking condition -- is_activity_scheduled..Condition -- Is Not empty. Check on message creation. Order At the beginning. I have attached the screen shot.

      This will update the custom field when the activity is moved from "Non Scheduled" queue to Some date (Scheduled) queue.

      This is working for me. Let me know if you have any challenges.

      Regards,

      Hardik Gupta

       

    • keerthi P

      Thanks Hardhik. Understood the use of is_activity_scheduled condition.  Let me explain my requirement in a bit more detailed way.

      1. We are working on Multi day tasks (with more than 1 segment)

      2. When the task is assigned to a technician, we would need to change custom status field to"Assigned" from "UnAssigned".

      So, we implemented

      1. Set property on Activity Add(Add to route) 

      2.  Blocking condition if the activity is added to a bucket so the status won't change to Assigned

      Issue, we are facing now is :  Set property is working at the segment level, i verified this using Rest API and can see the custom field value is updated. However, when i check this in GUI it still shows me old value(Unassigned) .  We understood that all custom fields uses master activity id property values while displaying in GUI. So, we some how need to either set master property using set property or display the segment property in GUI. 

      We also observed that:  in few cases set property automatically sets property at master activity id  . In few, it sets at segment level. We could not trace out the reason for inconsistent behaviour.

      Please suggest.

    • Hardik Gupta

      Hi Keerthi,

      The above condition I haven't tried with multi day segments. But according to documentation it is given as "In a pending multi-day activity all fields and custom properties are inherited by the segments from the multi-day activity with the exception of the Duration and Position in route fields which are determined for each segment".

      What I can understand is that if Master Activity is updated then all child segments should get updated.

      If a segment is updated then only the changes are applicable to that particular segment.

      Regards,

      Hardik Gupta