Skip to main content
Solved

Autorestart of singlestep Assistants - IFS Cloud

  • December 9, 2025
  • 2 replies
  • 23 views

Forum|alt.badge.img+4

I have created a singlestep and there is a requirement to autorestart the assistant after executing the Ok command.

But there is an issue with the autorestart functionality.

I do the following in my Ok command, where I execute function and get the output assigned to a structure.

As long as I don’t use the structure variable to assign attributes, as in above, the autorestart is working as expected.

But as soon as I put below highlighted code to assign the output value to my desired attribute, the autorestart does not work anymore. 

I tried to avoid structures as a variable and directly call functions and assign the relevant attributes with the output. But when there are multiple call statements, again the autorestart does not work.

 

Is there a solution for this?

Best answer by PhillBronson

@YashP very interested in more clarity in this area too
I have noticed inconsistencies as well when trying to rely on the client to do this.

The way I usually get past this is heavily rely on the plsvc to do all the data manipulation. In scenarios like this I would try to design the process so that you can rely on a CRUD_Update.
 

Here is a similar post dealing with inconsistencies in client execution:

framework execution sequence assistant | IFS Community

2 replies

PhillBronson
Hero (Customer)
Forum|alt.badge.img+11
  • Hero (Customer)
  • Answer
  • December 10, 2025

@YashP very interested in more clarity in this area too
I have noticed inconsistencies as well when trying to rely on the client to do this.

The way I usually get past this is heavily rely on the plsvc to do all the data manipulation. In scenarios like this I would try to design the process so that you can rely on a CRUD_Update.
 

Here is a similar post dealing with inconsistencies in client execution:

framework execution sequence assistant | IFS Community


Forum|alt.badge.img+4
  • Author
  • Do Gooder (Partner)
  • December 12, 2025

Hi ​@PhillBronson,

Many thanks for the suggestion.

I was able to get around the issue by implementing it in the CRUD_Update.

 

In addition to that, to keep the assistant still open, there has to be something happening after the database call. Hence, adding below highlighted code (having at least 1 assignment would do) on the .client is also necessary.