Hi.As Damith indicates, maybe the MCH_CODE value is changed by the PLSQL business logic of the entity after it has been changed by the workflow. You might want to try using the entity APIs:Entity Service APIs - Technical Documentation For IFS Cloud Note that they have to be activated first. Thank you much.Best regards.Gonzalo.
Hi Frank. I have done a quick test on CustomerInfo entity. I hope I understood correctly and that you can extrapolate this example to your use case. I try to set AssociationNo to ABC but the configuration made saves a predefined value ‘11111’. When saving… AssociationNo is automatically set to 11111. Here is what I did. Create a simple workflow named “bpaReplaceAssociationNo” like this: Configure a Projection Action on that workflow named “bpaReplaceAssociationNo”: Then use the form Customer to edit some values. When the record is saved, the workflow kicks in before the actual save and rewrites the value for key AssociationNo to ‘11111’. Then workflow ends and control is given to the actual save (PUT action). Then after save, the record is refreshed on screen with the proper value. Thank you much.Best regards.Gonzalo.
Hi Øyvind. As Yohan indicates information messages are not currently supported via workflows. Unfortunately, as far as I know, if you implement that information message with “Failure end event” you will interrupt the transaction so this is more like a validation message instead of an information message. Usually information message are just for letting the user know that something is happening but the transaction continues. If that is your case, maybe you can explore the User Interaction workflow: https://docs.ifs.com/techdocs/24r1/040_tailoring/500_business_process_automation/030_getting_started_with_workflows/#building_a_user_interaction_workflow In this kind of workflow you could pop-up a window with a non-editable textbox showing the message you want the user to view. It will have a button for the user to continue once the message is read. Thank you much.Best regards.Gonzalo.
Hi Sevim.You will need a combination of a Custom Event + a Online SQL action.First you need to locate the form you want to work with. Example: Get the System Info view open to locate the Logical Unit. In this case: The Logical Unit PurchaseReqLinePart is the one holding the Custom Event which should trigger when a new record is created. Create a new Custom Event here: You need to select carefully the table on which you want to place the Event. To make sure you are in the right place, it is good to have access to the database and check if the info you have just created is there. Select the attributes that you may want to check in the Event Action; you can use new, old or both values. It is possible to add some Custom Attributes that you might want. For example, if you want to get some specific information from Supplier for Purchase Part and there is a Get function for that, it’s easy to add here.Then complete the Action: In your case, the recommended approach is to use a Online SQL
Hi Laura. I’ve never had to do such things. OK, it seems like you would need to do some stuff to revert the situation. Please check if you can do all these things: Do you have the Request Release Update button available? You will have to click it and choose the version you want to use (23.2.4 for example) Maybe to have that option available again you need to remove the “release-update” branch in both Baseline and Customer Solution repo. If the “Request Release Update” button is not available you might want to open a ticket and ask Support if it is possible to have some manual steps done in the “backoffice” to restore to a previous situation. I believe the action you want to take is totally possible, but the only concern is that maybe the lifecycle experience portal is not prepared to achieve that without the help from Support/Lifecycle Experience team.Best regards.Gonzalo.
Hi Iskender. You might want to review the following documentation: https://docs.ifs.com/techdocs/foundation1/040_administration/240_integration/300_ifs_connect/080_message_archive/default.htm System administrators can use message archiving functionality to move processed and older application messages to Message Archive for future reference. This might very well be the reason why you see Application Messages disappear after one day or less. Have a look at the Database Schedule and its parameters: You will probably want to change the value for parameter HOURS_OLD_ to something greater that 24 (hours) Please have a look and let us know if that resolves the problem.Best regards.Gonzalo.
Hi Patrik. Unfortunately it seems that this integration API could have a bug since the RegDate is not designed to receive datetime. You might fill a ticket to report this situation to Support. On the other hand, it is also possible for your to use a regular API, the one that is being used by IFS Aurena web client. It’s not the best approach if you already have an API already designed for integrations. But in this case, the integration API seems to be problematic so you might follow Ashan tip and use alternative API. Best regards.Gonzalo.
Hi. Even that documentation indicates the following: Have you tried passing a date and time? Try passing the datetime using the following string format: "2024-04-24T15:01:00Z" Let us know the result.Best regards.Gonzalo.
Hi Ron.It seems like your integration is using a non standard projection “CPdmDataHandling.svc”. You will have to check with the functional consultant or developer who created it and check any documentation available associated to it in order to discover the reason for that error. Additionally you need to review which is the action (GET, POST, PATCH, DELETE) and the body content if any. Maybe there is error in the way the URL is invoked.Thank you much.Best regards.Gonzalo.
Hi Michael.There are no translations for Hindi in IFS Cloud but they can be added manually. Would that work for you? If so you can take a look at this similar question and solution:IFS Language for Country Taiwan | IFS Community Best regards.Gonzalo.
Hi Kalhari. You need to add the languages manually. Maybe that’s not clear enough. When you read in the documentation: Start by enabling the required languages. Visit the page “Used Languages” and make sure you set the languages in the red box as shown in the image below: Click on the “+” button and create the line for the missing language. Make sure you use the proper Language Code, RFC3066, NLS Territory…. The keep reading the guide and apply the next steps. Best regards.Gonzalo.
Hi Kalhari.I created a guide for a customer who needed to add translations to Operational Reports for non supported languages on IFS Cloud. This instructions will work fine to add translations to pages as well. Please find it attached. Unfortunately I don’t have documentation on how to achieve the same thing for Apps9 or Apps10. Thank you much.Best regards.Gonzalo.
Hi Kalhari.Do you need translations for IFS Cloud?Best regards.Gonzalo.
Hi Marion. I don’t know the exact details of the Sanity Build process. It might happen that the second time you triggered the Sanity Build some artifacts could have been reused and not computed again leading to a quicker run. Glad to read that this second time, Delivery was build sucessfully. I think I’ve seen this kind of situations before but I cannot explain why this second time it worked. Install in CFG and check if everything is OK; then move to UAT and PRD. Best regards.Gonzalo.
Hi. When you spawn a new DEV environment, you cannot select anything. It will take the latest sucessful sanity tag from “master” branch automatically.That’s why I’ve made this suggestion. You merge to master, run sanity build and once it finishes OK, you can order a new DEV environment and check if it is created without error. Have a try and let us know if it is created without problems.Best regards.Gonzalo.
Hi Marion. So you’ve made a modification, merged to “master” and run sucessful Sanity build. Before creating the delivery, did you create a new DEV environment? It would be a good check to verify that a new environment can be spawned using the latest commit tagged with a successful sanity tag. If you already did this and the environment was created fine, then I wonder if you have more logs information from the Delivery creation process so we can have a look at them and try to find out the cause of the problem. Thank you much.Best regards.Gonzalo.
Hi szebesta. It seems there is an integration/communication problem between the IFS Lifecycle portal and IFS internal systems where Customer sales information is kept. I think the best option is to create an incident using the Support portal. Provide all relevant details such as the action taken and error message. Thank you much.Best regards.Gonzalo.
Hi @K4uFredeL I think the installer will pick the INS automatically and deploy it. There should be no need to use the deploy.ini file unless you need to specify some kind of dependency for the INS file. If I’m not wrong the delivery installer will deploy the files in “database” folder in the following order:.CDB → .API → .APY → .INS @TheoB, let us know if you’ve been able to run the .INS successfully. Thank you much.Best regards.Gonzalo.
Hi @TheoB The location for this kind of files should be “<module>/source/<module>/database”. Here is an example for ORDER module taken from 23.1.0 Core code: Thank you much.Best regards.Gonzalo.
Hi Théo. You deploy an INS file on IFS Cloud environments using a delivery. The steps are:Register on JIRA or similar tracking tool the task you want to perform with the INS file The tool will provide you with an ID that you will use to generate the topic branch name for the INS file Create the INS file, commit the changes and upload to the remote Git repository Test the INS file using a topic environment and if everything is going well, merge to master branch Run a Sanity build Create a Delivery Install the Delivery on the relevant environments You can have a look at the following link in case you need to get more information about the Git workflow recommended by IFS to create modifications:https://docs.ifs.com/techdocs/23r1/020_lifecycle/030_customer_solution_development/010_working_with_git/020_git_workflow_examples/git-workflow-cl/ You also need some knowlege on Cloud Build Place to run Sanity build and Delivery processes:https://docs.ifs.com/techdocs/23r1/020_lifecycle/050_working
Glad to read it works! Thanks for letting us know. Have a good day.Best regards.Gonzalo.
Hi Randini.I haven’t worked with this functionality just yet but I found an entry in the documentation that maybe can help:https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/200_client_configurations/310_conditional_fields/100_conditional_lov/Thank you much.Best regards.Gonzalo.
Hi Stefan. Yes, the call to the external service should be out of the loop iteration. You would use the loop only to compose the payload. Then out of the loop, you would make the call using the previously calculated payload content. Isn’t this possible?Best regards.Gonzalo.
Hi Stefan.As we mentioned before, all depends on the API you are working with. Try to check their documentation to find out whether is possible or not to send that can of payload. Usually a proper REST design would allow only one record to be created using POST action. In the same way you can only PATCH/PUT on a single record. Same applies to DELETE. OData standard implements the batch concept. You can send multiple POSTs inside a single payload. Here is an example how it would look like: Check if your REST API provider support this mechanism or similar. Best regards.Gonzalo.
Hi Stefan.I’m afraid that your requirement doesn’t depend on IFS Cloud functionality. You are calling a 3rd party system using the IFS REST delegate. It is the 3rd party API that you are calling the one that should provide you with a way for creating resources in one single call. The way IFS Cloud allows to create multiple records using one single call is standard OData batch mechanism.Here is the standard documentation:https://www.odata.org/documentation/odata-version-3-0/batch-processing/Here is the specific IFS Cloud documentation:https://docs.ifs.com/techdocs/23r1/040_tailoring/300_extensibility/100_odata_provider/700_batch_requests/ But remember, the documentation above is only valid in case you wanted to call IFS Cloud from a 3rd party system. This is not your case; you are calling a 3rd party system from IFS Cloud. I hope you can check the OData batch mechanism with the 3rd party REST API provider and determine if it is possible to create mass data in one single call. Thank you
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.
