Skip to main content

Hi,

 

In the Activity Codes transaction, for dependencies we have 2 options: Pre requisite and Successor (not co requisite in this transaction).
I didn’t find a way to put an activity as successor.  (only pre requisite)

1/ Could  you tell me if there is a setting necessary to do that for an activity ?

2/  If we put an activity in a Service Guide (problem code) with Auto load : Should we have aslo the successor activity load to SV as sucessor without put it in the service guide ?

Thanks and Regards

anthony

 

HI Anthony,

I took a quick look at this and it seems there is an issue with the choosing of Successor in the dependencies.  If you select this and click Save, it reverts back to Pre-Requsite and does not save the Successor setting.

You should log a ticket for this.

As a work-around, I was able to save the Successor by selecting it and click Search instead of Save.  When I go into record later, it was still set to Successor.  Even if you click save again, it remains Successor.

What I suspect is happening is the state is not updated with Successor so when the Save button is used, it still populated as blank which then the default is Pre-Requisite.  Once the value is saved via the Search method (it does not have to reload like the Save does), it is committed to the database and retrieved properly.

Here is my example after using the Search method to save the record and then opening it again from the search screen.

 

 

Reply


Terms & ConditionsCookie settings