Hi Mark,are you referring to this? https://docs.thinkwisesoftware.com/docs/indicium/process_flows.html#13-api-triggerThis means I can create a simple process flow (send_e_mail) with a task as the starting point. From my original process flow the HTTP connector will post to Indicium Universal but then to the task. The body will be filled with the PK values. According to the documentation this will trigger the process flow because the task is the starting point of a process flow.Is the process flow (called by the HTTP connector) still executed as the application pool user? (in this case the authentication I put into the HTTP input parameters) If so, I believe this may be able to work.I'm going to try this suggestion soon.
Hi Mark,I've changed the starting point to a task. When testing a 403 error occurs.. The authentication is correct, I have tried it with multiple users. Trying to POST via Insomnia.JSON inputHeaders The process flow: Starting point is a taskTask configurationWhy do I get a 403 (Forbidden) response?
Hi Mark,all parameters are indeed Hidden. That includes the PK parameters.I can understand why this can be problem: Because the parameters are hidden Indicium Universal will mark them as unauthorized. So the service layer has no knowledge of the parameters.I’ll test this by changing the PK to editable and synchronizing to IAM.
Hi sjongmans,the SF already supports this feature via the ‘Subjects’ screen. Aggregation typesIs this what you're looking for?
Hi Mark,when the task is added to a menu the process flow seems to work when executing via the Windows GUI. However, after syncing to IAM and posting to the task via Insomnia a 500 error returns.The Indicium Universal log shows this entry:2021-04-08T14:58:54.4877187+02:00 0HM7L0TGG6E3I:00000003 [ERR] TSFMessagesMiddleware: An unhandled exception occurred while processing the request. (fffadd8a)System.InvalidOperationException: BeginExecuteNonQuery: CommandText property has not been initializedAny ideas?
Hi Mark,that's a bummer. Perhaps the documentation could be updated with this information (and maybe more info of the messages above)? So other developers don't make the mistakes/assumptions I make.I'll give it another go.
Hi Mark,it's working! The Insomnia POST to the task starts the process flow and the e-mail is sent.Thank you for all the help!
This would be very useful for procedures with the assignment type: SQL.
Hi @Erwin Ekkel,this is the complete path: “\\twisodev01.isodev.loc\ThinkWise_Software\Applicaties\EVO\Generated scripts\GEN_AUTOMATIC_SMART_PACKAGE\1.01\Deploy\”.However I don't think folders can be ‘absolute’ paths.
I've got it working on Indicium 2022.2.16.2. The file path is still the same. “\\twisodev01.isodev.loc\ThinkWise_Software\Applicaties\EVO\Generated scripts\GEN_AUTOMATIC_SMART_PACKAGE\1.01\Deploy\”The storage location for the process action is “\\twisodev01.isodev.loc\ThinkWise_Software\Applicaties\EVO\Generated scripts\”. Zip file inputAt first I was confused because I couldn't find the created .zip file. But after reading the documentation more carefully I came to the conclusion no file will be created: Zip file outputSo I added a ‘Write file’ connector to create the .zip file (by using the binary) on a different storage location.Zip folder to binary and write zip file to a storage locationWrite file input
Hi Jeroen,thanks for your answer!Till this moment we have no errors that are a result of these validations.Because we create such references on purpose, we will analyze the ones we have and approve them.
Already have an account? Login
Enter your username or 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.