@jasahu From our experiences, if any Quick Report would get touched it would refresh the cache, which made sense. Most of the time the refresh didn’t take a lot of time, came back and the user didn’t even know the wiser. Just the occasional refresh that dropped certain Quick Reports. We also adjusted when we updated and/or installed Quick Reports into production to prevent fewer cache refreshes. And yes, we just created a service that we run all our Quick Reports like this through. Since implementing, I haven’t really looked through our logs to see if it is still happening. I also haven’t received any support calls for it after we trained our users over it and explained to them what is going on. One odd thing that we discovered is that this almost always happened to us when we updated IFS and even applied the occasional patch. So we made sure in our scripts we called that API when it was all done. Thanks, this is really good to know.One thing I am still trying to find ou
@jasahu We ended up putting in a “solution” where when IFS would throw an error that it “Couldn’t find Quickreport….” (paraphrasing that) we would catch that error and then call a custom action that would call Dictionary_Sys.Refresh_Odata_Projection_Cache(“QuickReports”, “”). Alerting the user that whatever they were trying to do failed and to try again. Most of the time, the refresh would be done by the time the user tried it again and wouldn’t see the error again. Or the refresh would still be happening and then once finished it would be there. We have updated IFS a couple of times since this issue, but I can’t say with any confidence that it would be resolved. We haven’t had the issue since putting in this solution. But it also may never be happening anymore either. Hi @hansend,Thanks for detailed info, that is quite a trick.Just be sure if I understand it well:Does the error occur without you touching the definition of quick reports involved?You just keep using the solution
Regarding my last post up above, maybe @SeeingSharp can you please tell me more about your comment on this dated from Sept. 22nd ? Thanks in advance Hi @HDAL, @SeeingSharp,Do you have any new of positive developments here?We are interested in it too… regardsJanos
Hi @jasahu @kvbe , Are there any cascade workflows associated with this asynchronous workflow execution? If there are errors related to executing the Workflow they will be logged in oData logs. Please see if any errors logged there. In addition, starting from 24R1, we are adding error details to the Async table if there are any errors during execution. Additionally, from 23R2 onwards, we have implemented asynchronous observation capture for troubleshooting purposes. These features can also be used for troubleshooting Async Workflows. Async executions do not provide immediate notifications to users in case of errors. If none of the methods are successful in locating the error, please raise a ticket to IFS Support for further investigations. Thank you, Yohan Hi @yohan, No cascading workflows are involved.Thanks for all these improvements!
Hi @jasahu The Unicode database character set AL32UTF8 is the recommended database character set for IFS Applications. Pls refer to following links on how you should use ASCII characters in IFS applictions https://docs.ifs.com/techdocs/Foundation1/050_development/040_core_server/027_base_server_dev/100_localization_internationalization/070_Unicode.htm https://docs.ifs.com/techdocs/Foundation1/050_development/040_core_server/027_base_server_dev/010_model/900_base-serv-mod-ref/120_plsql_source/600_hints/100_illegal_string_characters.htm The example below shows how to write the Swedish word "LEVERANTÖRSFAKTURA" as a string where the Swedish character "Ö" is above ASCII 127. DECLARE string_ VARCHAR2(100);BEGIN string_ := 'LEVERANT'||UNISTR('\00D6')||'RSFAKTURA';-- or-- string_ := UNISTR('LEVERANT\00D6RSFAKTURA');END; The example below shows how to use ASCIISTR to find which hex code to use in UNISTR: SELECT asciistr('Ö') FROM dual;ASCIISTR('Ö')-------------\00D6 /Harshi
@yohan @jasahu did you find a solution for this problem? We are struggling to understand why workflows are getting stuck in IP state. How did you do the retry option in the workflow? Hi,Unfortunately we could not find a solution for this ‘getting stuck’ thing.So we decided stop using workflows for background style processing as this problem seriously hinders usability and went back to conventional PLSQL solutions.It is sad because we put a lot of work in it, but eventually came to the conclusion that BPA in background is not ready for production use in general.
Hi, Where can we find this setting in App10? The wizard step the image shows above does not exist in Reconfig in App10 UPD17. Ok, we found the answer for App10, it can be set in ‘IFS Middleware Server Admin Console’
Hi,Where can we find this setting in App10?The wizard step the image shows above does not exist in Reconfig in App10 UPD17.
Hi @StartStop, It is done as it is described here:Currency Rate Update (ACCRUL) - Technical Documentation For IFS Cloud
That is quite sad news for us…It seems we need to drop the idea of using workflows for the purpose of currency rate updates in the background because it is a must to be able to know whether is was successful or not and also every possible kind error not only the one mentioned above and having extra workaround like logging errors into a some new table sounds really cumbersome.Actually it is quite strange that this feature is missing (background workflow failure notification in any way to the client) I think it seriously hinders the usability of workflows when it comes to background processing.Anyway, thanks for info, we are wiser now than before :)
Thanks for info. Unfortunately I did not get much closer to the solution as the workflow apparently runs fine when in debugging mode.Anyway, I deployed this workflow to another system it works well there!So it seems something somehow is stuck regarding this workflow in the original system. So moving forward I have another problem now:How to get notified - at user level - of errors in the workflow execution when run in background?This workflow will primarily run in the background, started by a background job.I deliberately put some error in the workflow and I get no notification of the error.The background job that starts it gets to ‘Executed’ state without any errors or warnings.What is the solution here, how can one see when the workflow execution in the background runs into an exception?
So it made me realize why you said there was no WSDL in App10 (or App9), because PL/SQL Methods Webservices is different thing (https://docs.ifs.com/techdocs/foundation1/050_development/024_integration/020_webservices/020_plsql_methods_webservices/default.htm). It required a bit of modeling, not only setting up routing. And it produced a WSDL too. It was not the PL/SQL method that generated a WSDL. And you will never be able to generate a WSDL file from the PL/SQL code. The WSDL came from the model. But you won’t have such a model in IFS Cloud. So, if it’s essential to have a WSDL file, I see 2 options: Create the WSDL file manually in any text editor Use any Apps 10 environment where you can create the model, generate the WSDL file and than just slightly modify it in a text editor. Best regards, Heinz Manual editing is not really the way to go for us (revision tracking over time., etc.). So I started to get used to the idea of solving it without a WSDL.Thanks for
No difference in routing to Apps 10. Just create a routing address with type PL/SQL and then use this address in a inbound routing rule. Choose no queue (as it should be synchronous) and use a content based routing (e. g. check for existence of a special node). Best regards, Heinz That sounds good, thanks!In the meantime I found what the WSDL looked like in App9:http://<host>:<port>/ifssvc/<Service Name here>?wsdlLike this: So it made me realize why you said there was no WSDL in App10 (or App9), because PL/SQL Methods Webservices is different thing (https://docs.ifs.com/techdocs/foundation1/050_development/024_integration/020_webservices/020_plsql_methods_webservices/default.htm).It required a bit of modeling, not only setting up routing.And it produced a WSDL too. Anyway, your solution would be good too if there was a WSDL attached to it.Otherwise I would feel embarassed to tell the 3rd party:“Sorry guys, no WSDL”, because that is a necesary accessory of a SOAP i
Sure it does. The PL/SQL method still must return a CLOB. That’s the synchronous response. Best regards, Heinz That is interesting, can you please give me more info on that, a screenshot maybe, how the routing is set up?
You can still route incoming XML messages to a PL/SQL method. No change between IFS Applications 10 and IFS Cloud. Used it several times and still works fine. Best regards, Heinz Perhaps we do not mean the same thing, I am talking about a SOAP webservice which expects a response. Does your solution cover that too?
I have not reported it to IFS because we needed an quick fix (and from IFS we could not expect that) as this bug can have major consequences , once it occurs the only workaround was to restart App Server.So we fixed it locally in QuickReport-Cust.plsql: @Overtake CoreFUNCTION Validate_SQL_Expression___ ( validate_status_ OUT VARCHAR2, stmt_ IN CLOB, is_import_validation_ IN BOOLEAN DEFAULT FALSE) RETURN VARCHAR2ISBEGIN$TEXTSEARCH WHEN OTHERS THEN dbms_sql.close_cursor(cursor_); validate_status_ := 'INVALID';$TEXTREPLACE WHEN OTHERS THEN --(+) 230215 JASAHU C_U01-3 (START) IF dbms_sql.is_open(cursor_) THEN --(+) 230215 JASAHU C_U01-3 (FINISH) dbms_sql.close_cursor(cursor_); --(+) 230215 JASAHU C_U01-3 (START) END IF; --(+) 230215 JASAHU C_U01-3 (FINISH) validate_status_ := 'INVALID';$TEXTEND END Validate_SQL_Expression___;
Ok, the answer is quite easy, all components mentioned in the original post (Connect and Spin) seem to be present, so just :1.Create a service task, where ‘Implementation’ is ‘Connector’: On the Connector tab, set values similarly to this:
Hi Gonzalo, Regarding App Msg creation via Custom Event:That could work, but this is more complicated than what I wrote above using ‘ImportMessage’, but good to know as an alternative. Regarding outbound SYNC:It is not about he connector being sync or async, it is about the message itself being sync.That means that the message does not get into any queue (like OUT1), but it gets executed immediately.Action of type ‘Application Message’ of a Custom Event cannot do that that is always async.Plsqlap_Server_API.Invoke_Outbound_Message would do that in SYNC for me, if there was a way to call that from Workflow. BRJanos
We have an integration task, and have to communicate with the other app by way of files so I need to create an outbound app message which will become a file sent by FILE_SENDER. And I am also interested in outbound SYNC app messages as well, to see how much we can accomplish in the future.
Yes, Projection Delegate could work too, provided I have the proper projection.ApplicationMessagesHandling.svc or ApplicationMessageHandling.svc do not seem to help me, no possibility to create new msg.Interestingly, ApplicationMessagesLobbyHandling.svc seems capable of creating app messages, in 3 steps, via action ImportMessage.But is that the best option out there?App message are far more important than getting such a bad treatment.
Hi Gonzalo, Thanks for info on calling REST, that is useful, but my point was the creation of an Application Message.Which would go to IFS Connect, get routed to an address and so on.REST would definitely be one way to do that, but I cannot find the API for that purpose.Do you have some idea on that?
The answer to this is based on this info from Oracle doc:Preventing Malicious or Accidental Access of Open Cursor NumbersAn error, ORA-29471, is raised when any DBMS_SQL subprogram is called with a cursor number that does not denote an open cursor. When the error is raised, an alert is issued to the alert log and DBMS_SQL becomes inoperable for the life of the session.If the actual value for the cursor number in a call to the IS_OPEN Function denotes a cursor currently open in the session, the return value is TRUE. If the actual value is NULL, then the return value is FALSE. Otherwise, this raises an ORA-29471 error.As of App10/UPD18 there is at least one place in the program that may try to close a cursor which is not opened (as happened in our case) Quick_Report_API.Validate_SQL_Expression___, we fixed it ourselves, using the technique in #1 below.There might be other cases like that.The key part is what is bold above.So after this happens, those parts of code, anywhere else in the s
Hi @Abhilok, @knepiosko,We have the same problem, have to managed to find a solution for this?
Hi Charith,Ok, I understand that no automacity exists for this. On the other hand, when it comes to secrets, in our case it would not be a secret as this file is freely downloadable from the other party we want to communicate with (only public key in .cer file). Anyway, it is good to have reliable information on this topic.Thanks :)Janos
Hi @InfFilipV,This is good news, thanks, I will consider it when next projects will start.On the other hand, we got this official answer some time ago (sent you in direct email at that time, August 2021): The community post is updated and following is the expert advice. ISD does not support having multiple versions of the same component. It is not intended to be used like that. In particular with the Global Extension the expectation is that the GET components are not included in the RRC/CIFX file and should also not be fetched from the archive directly. Instead the GET components should be merged and checked into harvest. An RRC file can contain contain components in multiple archives. This is for example used for the HR components which are in the MEE archive. As the MEE components are all completely new components and there is no overlap this is save to use and this also works OK in ISD. Only when having the same component in both Core and another Market/Archive then it is not suppor
Already have an account? Login
No account yet? Create an account
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.
