Skip to main content

Hi,


In Alliance, for a service order, the first activity is defined as Primary Activity.

Could you  explain the meaning/goal of this primary activity : Is it for technical view  ?

Could you explain if there is a way to define which activity could be set as primary (unless with stop code)


In a customer case, we have 2 activities, all of them have the same weight for functional perspective.
 



Thanks and Regards

anthony

The primary activity is always the first activity created for the order and ‘owns’ the order.  This is why it is primary.

There is not an application functionality where you can choose which activity will be the primary.  The stop codes such as incomplete can create a new activity and that activity becomes primary if you stop the primary activity as incomplete.

Also, if I am not mistaken the primary activity is the only one which can resolve the order from mobile with some MOE settings.

 

You can adjust the default/first activity that is automatically created in the Workflow (Service) module (that won’t help from a weighting perspective but you can change that to an activity called Primary Assign or Default Activity or something along those lines so it’ll be more obvious to the end-user that it’s the standard activity that exists on all service orders):
 

Thanks,
Reid

Correct, this defines the activity code assigned to the first activity. This default setting also could be overridden by an activity populated by the service guide should one be defined thus ignoring the default setting.

Point is, activity # 1 is always the primary no matter what activity code is used within activity # 1. 
 

Reply


Terms & ConditionsCookie settings