Hi @dritter, The problem unfortunately is with the data entering the workflow. As long as that happens, the engine breaks (even if you remove it in your first step). Currently there is NO workaround and it has been acknowledged as a limitation (as far as I know).
Hi @jloveall, I have a similar problem. It's good to know that the contexts are only layers on top of the global context. How I do it:After the upgrade unpublish all pages where the baseline has changed Start at the page config page, filter on baseline behind. Select a page and go to designer. Start with the global config Expand the changes, apply baseline and revert the configurations which were deleted. Save → Publish Continue with the next contextI do agree that this seems to be a lot of work which needs to be done every Release upgrade (and sometimes in Service Updates as well!)
@ibalfe, unfortunately with the current information it's unclear what the payload structure is like. Normally with an array you can use something like ValidationRec[0].ValidationRec.etc.In this case the variable might be refering to a record in a different projection with the “com.ifsworld …...”. Could you post the entire payload or reponse JSON here?
This requirement has been dropped
@MelTanyaS,We have multiple environments.On a test environment:Do a quick test first. Disable all event actions and do the test scenario, does it work? Then it is likely a similar problem. Re-enable them again.We made an export of all event actions We made a ranking of which entities were more likely to impact the process opened 2 sessions, in one we have the event actions which we disable one at a time. On the other session we have the process at the step where we were getting the issue. At this point you will have to disable an event action → press the save button. Rinse and repeat until it does work After you find which causes the issue when enabled, re-activate all the previous ones and try again. Sometimes the issue can be caused by multiple items.
Hi @Asadan , This is correct. We had a similar problem on the 22R2. After installing the SU it functioned again. We do not have the JOBRM module.
Hi @ishtiaq , You can find the query behind a custom page by:Opening the debug console (top right)Expandign the support console at the bottom Selecting the SQL button and selecting a record
Hi @MelTanyaS,Could it be that there are automations on the purchase order or other related entities?I’ve had a similar problem in the Cloud version and it turned out that some processes (Incoming Customer Orders) Do not fare well when automation is doing changes in the meantime.
Hi @Pierrick ,We just upgraded from 22R2 to 23R2. I still have my bookmarks although one of my images dissapeared. I quickly did a check but could not find any documentation that it would be removed?
Hi @NPGIFSJOMAII ,Sharing my experience.We are currently not live yet, but the only way we see to create large amounts of part creation is to make Migration jobs. While I agree that it is not very user friendly, I think it is good to have standard procedures in place to make sure that the data is complete.At first I was worried that end users could change the definitions or update values but this is pretty managable. You can set the rights to what the job itself is allowed to do in the job itself (New/Modify): Set which users can see the jobs at all: But also set what the user is allowed to do (only execute jobs)
Hi @kacperifs, I'm on version 23R2 in case there are any differences.It should be possible to add a custom attribute according to the entity itself. The most likely reason that there is no relation between the tables is because there is no direct relation between the tables (Many to many). There could be many deliveries on an order and because of this multiple invoices as well. This could cause you to retrieve an incorrect value. Having said that, you can use a quick report to do an create a sample query.In this case I think what you are looking for is something along the lines of: SELECT Latest_delivery_dateFROM Customer_Order_Inv_Head COIH WHERE COIH.CREATORS_REFERENCE =’[ORDERNUMBER]’ ANDEXISTS(select * FROM Inventory_Transaction_Hist ITH ITH.SOURCE_REF1 = COIH.CREATORS_REFERENCE AND COIH.ORDER_NO AND ITH.SOURCE_REF_TYPE_DB = ‘CUST ORDER’ )FETCH FIRST 1 ROWS ONLY However again, I would emphasize on rethinking what exactly the goal is here.
@TheoB , this seems like a bug, I've reported it on case CS0210725.You get this error when opening locally, but also while fetching it from the server. This renders this version of report designer useless.This version seems a bit broken. Connecting to an environment when already logged in also causes a issue to me in version 200.3.0000. As Marcel suggested, I would recommend going back to the previous version.
Hi @rfedorchuk, Do you have any more info on this? The error you initially posted doesn't seem to be the issue as this is a normal notification which is added to every migration job execution.aren't there any errors in the migration job execution regarding the lines?In this case since it's creating a table from file, this could only indicate it has something to do with the filelayout or content.
I have regular meetings with IFS R&D regarding the new workflow functionality.CURRENTLY IT IS NOT A MATURE SOLUTION YET.I would not recommend moving to workflows anytime soon.While IFS stay purposefully vague with when sql would be depricated, they won't remove it until at least 24R2 and if you would be on that version, you still would have 23 months to move to Workflows.My expectation is that they won't remove it for a long time, if ever.Performance wise, the new tooling is not anywhere close to SQL standards.
Hi @EPSDANMI , This should be possible. More information regarding the setup can be found here:Configuring Windows ADFS - Technical Documentation For IFS Cloud
@paul harland, IFS has fixed the issue of payloads being too large from version 22R2 SU17 onward.
Hi @paul harland, Coincidentally I am working with IFS to improve their Workflow tool. This issue is not specifically because of the number of characters used, but a variable that can only contain 64kb max. I've been told (yet to verify) this is the same variable containing the workflow .bpmn file and is set to 1 MB max from 23R1 onward.
@dfsjmarchant , Did you manage to work out the details of your specific scenario?
Hi @dfsjmarchant, It depends. If it is based on a diferent field that would be possible too. In that case you would have to create a read only field and the query would be SELECT CASE WHEN :VARIABLE > 0 THEN ‘TRUE’ ELSE ‘FALSE’ END FROM DUAL This is a dummy statement where you would have to replace the variable with your variable,The argument is the column which is the field containing the 0/1. the argument could be v.customer_no (example). then the query would be “SELECT CASE WHEN :CUSTOMER_NO > 0 THEN ‘TRUE’ ELSE ‘FALSE’ END FROM DUAL “
Hi @dfsjmarchant, I'm unsure if this will completely cover every situation. I will describe 2 options.Option 1:If you want to stick to the 0/1:I'm assuming that there will only be 2 statusses:0 (false) and 1 (true).I would recommend creating a custom enumeration where db value = 0/1 and description is false/true Go to custom entity and press + create a persistent field with type enumeration and select the custom enumeration. Use the switch boolean To determine which value is true and which value is false Option 2:If you don't specifically want to stick to the 0/1 statusses. There is a standard enumeration Named FndBoolean which contains True/False value.Go to custom entity and press + create a persistent field with type enumeration and select the enumeration FndBoolean . Use the switch boolean To determine which value is true and which value is false
@EILCTHOMPSON , I can second this (3-4 days). There are several steps you have to start and it will run online (applying Release update, running sanity build, & creating a delivery environment). The online services will do most of the work. Nowadays in the upgraded documentation you have a pretty good idea of the steps you'll have to go through. Release Update Studio - ALE Documentation For IFS Cloud
@BLLBrucemo A little off topic.As a customer coming from a different ERP to the IFS Cloud 22R2. At this point having a similar implementation timeline as @ShawnBerk, not live yet. Our biggest painpoints are:Not enough knowledge of the platform. Also from IFS side their teams are still discovering how everything works (Developers & Consultants). Lots of bugs Lots of design mistakes Lots of illogical design decisions A still growing list of limitation (based on the 2 previous issues) Some flip flopping from IFS regarding important subjects (Discontinuing online-SQL, Camunda workflow engine as replacement) Lots of basic functionality that is only present in later versions (23R2+) Playing tug of war with Support and R&D regarding potential blocking issues No maturity in error messages/troubleshooting At this point (22R2) I would not recommend anyone moving to IFS Cloud.
@Tomas Ruderfelt, Unfortunately I've tried that as well but in the current version (22R2) the GET expressions are not working to select properties. Only work around now is to put a fixed value there like dummy.Thanks for your answer!
@Charith Epitawatta, Thank you for the notification it's fixed in a future version. That does leave me in a pickle now.@Marcel.Ausan , The link seems only to be available for partners (that's why I also couldn't find it in the first place probably). I'm going to send some messages to see if they can open it up. It doesn't make sense to block off important posts and then the same questions getting answered again.
Hi @UKh, regarding the User:Is it possible for you to use the CurrentUser variable instead ? That seems to work in my example (22R2). Regarding the selected printer:Unfortunately this looks like it's picked up AFTER the report rules apply making it unfeasible to do it that way. The functionality of the screen is just generic so it is available in the screen even though it has no function in that specific step yet.I would recommend finding a different way of identifying when this rule should apply (since I'm guessing you want to SET the printer to no printout as seen from your example).
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.
