Hi Joana,Sorry, but I haven’t worked with the FSM product for quite some time now and don’t remember such detail here, guess this is not supported though unless this has been enhanced in recent versions.Best regardsMartin
Sounds like uncommit is happening, try to query “DSP” in events and/or Uncommit - Check your commit rule settings. Notice when NO rule is defined then some default settings will apply. My experience to avoid such behavior you should always have an active commit rule./MArtin
Not an expert in Rest api, but PSO uses some internal id’s you can see in different areas. For instance on the scheduling dataset you can see the latest internal id. I think these are the same id you can see in the audits table. So I would expect that such a returned internal id can be traced in audits or failed audits.
Thanks again @Kasia /MArtin
Thanks @Kasia I’ve been looking around there, why I asked :-) Don’t we have a brochure or something more appealing introduction - Or do you have a more specific link?
@joana.m.machado I can’t say I know much related to rest calls in FSM, but I would say this should be feasible. Could imagine though the polling broadcast reference might be a challenge.@Rob Oldenburg anything you can confirm?
@AndreiaLeitao note that the blocking will expire after the set timeout. Blocking is actually the most used approach. The Non-blocking feature were introduced later in order to handle activities with dependencies better. So if you do not use such dependencies it should work fine with the blocking.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.