kipkingle
Active Member
The new Solution Modeler does not allow you to send messages when you attach a form link. In the past, I could send a message through workflow and attach any form to it. My code within the send message looked like the following:
Send Message (BF Address Book, <Claims Queue>, “Claim Rejected”, <Blank>, Call (App48201, Form:W948201F, LM55002, <None>)
Now when I setup a simple workflow (Start ->SENDMSG->END), the program will always error out on the SENDMSG because the form that it is attaching does not contain the alias SERK in the Data Structure. This is a new requirement and GSS claims that it is working as designed. If you go forward and update the form you are calling and insert the SERK into the data structure, the workflow will send a message. Unfortunately though, the workflow will not complete because it expects a value back from the SERK.
Has anyone else noticed this issue? Does anyone have a potential work around? One theory that I want to test is to call a UBE that sends the messages. I know I can use the system function “Send Message” in a UBE and it does let you attach forms without the SERK.
Send Message (BF Address Book, <Claims Queue>, “Claim Rejected”, <Blank>, Call (App48201, Form:W948201F, LM55002, <None>)
Now when I setup a simple workflow (Start ->SENDMSG->END), the program will always error out on the SENDMSG because the form that it is attaching does not contain the alias SERK in the Data Structure. This is a new requirement and GSS claims that it is working as designed. If you go forward and update the form you are calling and insert the SERK into the data structure, the workflow will send a message. Unfortunately though, the workflow will not complete because it expects a value back from the SERK.
Has anyone else noticed this issue? Does anyone have a potential work around? One theory that I want to test is to call a UBE that sends the messages. I know I can use the system function “Send Message” in a UBE and it does let you attach forms without the SERK.