Hi @JOOLSE , Thanks for the reply.Yes, for the attributes we have provided the translations for traditional Chinese, we could see them on Android phones as shown below,
Any plan to support Parallel dev for Aurena Development in IFS Cloud as well?
Hi, Apart from what we have in Tech Docs, do you have a quality Check list or an AQS created separately for IFS Cloud version as well?
Many thanks @Rifki Razick
@Rifki Razick , For customers in 22R2, what is the recommendation from IFS to deliver workflows, and version control in GIT? Thanks
23R1 User Journey experience so far :)CS0144998 Request Release Update problem Fixed by Thor after escalated on 6/6/2023 CS0144427 Error when applying "Apply Release Update in Baseline Repo" 23R1 SU1 CS0145435 Error when applying "Apply Release Update in Baseline Repo"(New issue found on 6/7/2023)
We moved to 22R2 SU7 and got the above error from customized layouts. Any suggestion to resolve?
I fixed this issue, by removing the Token credentials for git in Windows "Credential Manager" at Control Panel\User Accounts\Credential Manager. The next time I tried to connect I was asked for visualstudio.com credentials and the cloning succeed.
I previously had Technician & Customer-solution dev roles assigned and everything worked until yesterday. Suddenly, I got the below error when accessing the repo from GIT but I can access repos from Azure without any issue. remote: TF401019: The Git repository with name or identifier customer-solution does not exist or you do not have permissions for the operation you are attempting. Then I got the information, having several roles are not recommended and that may be the issue for this. Then Customer-solution dev role was removed but I still have the same issue. Any hint bypass this error?
Hi @stefan,Many thanks for detailed explanation, helps a lot. One more question, is this same rule apply in ALE(customer build places) when creating topic, sanity and delivery? Here do not have short lived environment created on the fly based on a sanity image and not sure what is the base to fetch a module as a fresh or version up-to-date, specially upon a new delivery creation from ALE portal. Appreciate if you can elaborate this a bit if any changes to the explained above. Thanks,Chamila
@mmoss , below is the workaround suggested in the Jira issue. Hope this helps! It worked for me :). In this case, the Add Contact is an Assistant is called from outside, not defined in the Business Opportunity page itself. That is the reason why it is not shown in Page Designer. It is designed in that way to keep down the projection size, which is related to technical requirement to improve the performance.The workable option here we are left with is as follows. Identify the client model for Add Contact, which is called from outside. Here, it is "AddBusinessObjectContact" client model. * Open a "Dummy" page and configure the Page Designer there. 2.1 Use below as the URL and go to dummy page:<host>/main/ifsapplications/web/page/AddBusinessObjectContact/dummy(The client will give you a 404 stating that page not found. It is fine and still can open page designer.)2.2 Now open page designerGo to "All Pages" >> "Assistants" >>“Create Business Object Contact Assistant” >
Many thanks for all your replies. This is really a helpful information.
This means we have to send the configurations to CFG first via delivery and then IAL?Yes, this is best way to handle it. If you need to send both at the same time through the automation, you need to write two scripts for custom field(publish first) and IAL(may be as ins) and list them in the deploy.ini. In IFS Cloud, we cannot change the install.tem.But I prefer to do directly in the use place without having them GIT. But R&D suggestion is to version control all the configs as well. I think we need a discussion here for that. .
Hi Wasana,Provisioning environments in the BP, consider only what we have version controlled in GIT.How did you handle custom fields? Are they in GIT or directly uploaded?But again even you version Custom fields, it will not publish automatically upon provisioning. If you refer a configuration(custom field, view, LU, etc. ) in some other place, it should be installed and published in the database prior to its use.In legacy systems prior to IFS Cloud, We created a script to make it even publish to avoid such issues. You may need to modify the deploy.ini to set the correct order of deployment as well. Best Regards,Chamila
Thank you so much @praveen.geevinda. That really helps!
Found the following workaround and it worked.[3:53 PM] Masheesh IkramChamila Peiris We had a similar support issue and this can be due to when you have separate projection and client for assistant. So the assistant is not part of the page. Please refer the last comment for a workaround in https://ifsdev.atlassian.net/browse/CRMZSPPT-799
I also have a requirement to hide certain fields in the below assistant from Page Designer. Is that possible or any other option?I cannot even find that assistant in the age designer as mentioned above
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.
