I think you can do that validation step within the workspace that's used for the Server App and then use a FMEServerJobSubmitter to start the workspace for step 3 & 5
If you have workspace 1 publish to a data streaming service you can have all the user communication in there. The only tricky bit would be step 4, but if you post a message instructing the user to go back to the initial form I think that could work.
I think you can do that validation step within the workspace that's used for the Server App and then use a FMEServerJobSubmitter to start the workspace for step 3 & 5
If you have workspace 1 publish to a data streaming service you can have all the user communication in there. The only tricky bit would be step 4, but if you post a message instructing the user to go back to the initial form I think that could work.
If you're really clever the initial DataStreaming result could be a webpage (e.,g HTML) which has the ability to make a subsequent rest call to FME Server. But to be honest I think @Hans van der Maarel suggestion is enough
I think you can do that validation step within the workspace that's used for the Server App and then use a FMEServerJobSubmitter to start the workspace for step 3 & 5
If you have workspace 1 publish to a data streaming service you can have all the user communication in there. The only tricky bit would be step 4, but if you post a message instructing the user to go back to the initial form I think that could work.
Thank you, @Hans van der Maarel , for your reply.
I'll have a look to the FMEServerJobSubmitter. Is it only a background process or if it will give the user feedback ?
I may have a look to @virtualcitymatt suggestion too.
About Webhooks, is there a way to capture "currently logged in user" since it is using a Token ?
Thank you.
Thank you, @Hans van der Maarel , for your reply.
I'll have a look to the FMEServerJobSubmitter. Is it only a background process or if it will give the user feedback ?
I may have a look to @virtualcitymatt suggestion too.
About Webhooks, is there a way to capture "currently logged in user" since it is using a Token ?
Thank you.
While I haven't tried it you can see if these give you what you're after. I suspect what is returned will be the owner of the token
Thank you, @Hans van der Maarel , for your reply.
I'll have a look to the FMEServerJobSubmitter. Is it only a background process or if it will give the user feedback ?
I may have a look to @virtualcitymatt suggestion too.
About Webhooks, is there a way to capture "currently logged in user" since it is using a Token ?
Thank you.
The FMEServerJobSubmitter just submits the job, there's no feedback there
I think you can do that validation step within the workspace that's used for the Server App and then use a FMEServerJobSubmitter to start the workspace for step 3 & 5
If you have workspace 1 publish to a data streaming service you can have all the user communication in there. The only tricky bit would be step 4, but if you post a message instructing the user to go back to the initial form I think that could work.
Thank you for your answers,
I finally went with @Hans van der Maarel idea.
Only problem, so far is when I go back to my form, using the back button of my browser for example, the form is blank. Any Idea on how I could go back to the values that were entered by the user ?
Thank you again