@TheoB, unfortunately there is no easy way of doing this. Translations are managed in the “text translations” screen. Here you can see all the translations. To export these translations you can export all translations (core + config) by:Run the attached query through quick report and export (you might still have to import the query through “import configuration file(s)” navigate to the “export language files” page select “export translations file” & correct layer and press [next] select the type and press next select the module(s) and press next Select the languages and press nextThis will generate a zip file which you can import by:Unzipping the zip folder navigating to the “import language files” page. Ticking the “import translation files”,”run as background job” and "refresh dictionary”, Unfortunately it is not possible to export specific translations.I have this setup because after every service update the core translations are reset. Since we as a customer have changed tran
Hi I'll add the necessary fields in the attachment but for the example please follow this step plan.Step 1 upload and deploy the bpmn workflow file. Import the custom fields through “import configuration file(s)” Publish these custom attributes on entity configuration (Entity DocIssue). Under the Entity configuration on the DocIssue entity, select additional views at the top and enable the DOC_ISSUE_REFERENCE. Synchronize the configuration at the top of the screen Import the custom event through import configuration file.Now for the explanation. The custom attributes are linked to the core table through the Objkey view column. IFS filters out the objkey's for the end users because these are DataBase GUID's and end users have no use for them. After setting this up you can create a custom event and action on the CFT (CustomFieldTable) where you will pass the NEW:ROWKEY value. Now for the workflow part, I've made a simple example. The first step is a projection action where we will filter
Hi @EntUviniG, We I've had a similar problem in the past. In this case, make sure that you pass the NEW:ROWKEY value.Also add a custom field on the entity DocIssue Read only → Expression v.objkeyAfter publishing this you can do a read on the document issue set using the filter cf$_objkey = ‘${ROWKEY}’ This should retrieve the specific record you're looking for.
Hi @Wafaa, we experienced this as well and this was reported as a bug.It is fixed in 22R2 SU14.
Hi @paul harland , Currently I've had payloads in workflows of over 4000 characters. For the workflow itself this does not seem to be an issue. However when troubleshooting the UserInterface only supports value fields up to 4000 characters (meaning that the UI stops working in the workflow pages).
Hi @Asela Munasinghe ,Before this ticket I've tested it in the Cloud version as well. However, there were some discrepancies which I wanted to check with the documentation.I've created some support tickets to get some (probable) bugs fixed.Thank you for your answer.
Hi @Asela Munasinghe Asela, Thank you for your quick response. Unfortunately this does not fully cover my question since I still don't know what parts are or aren't copied with this functionality.
@romsar, that is correct. A custom field is always linked to one single entity.If editing IS NOT required in the other screens , read only fields can be created on the Entities and added to the pages.If editing IS required in the other screens, separate persistent fields have to be created and events/workflows are required to update the field.
Hi! I've had similar issues, the way I started troubleshooting:Unpublish pages Check if you can open the API documentation in the API explorer case. Check if there is a projection configuration of this entity published and unpublish, export and fully remove it.Unfortunately IFS does is not really a big help when troubleshooting.I hope this helps to finding the issue! BR,Jonathan
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.