Key user extensibility in Fiori client – part 2
Part 2 and 3 consists of various videos and how-guides to achieve different tasks for a key user.
1. Create Extension fields
Here’s a short video on how to create an extension field. There example here is to create a field of list type on the account screen.
2. Property Rules
2.1 Create Rule
2.2 Assign to Field Property
Note: If a rule got assigned in HTML5 it will be shown correctly in the adaptation side panel in Fiori. But if removing this rule assignment by using the (X) icon does not work correctly, then you can delete the change transaction. You can follow the steps shown in the ‘Delete Change Transaction’ video published in the part 3 of this blog series. The type of changes from HTML5 is “AddCondition” while in Fiori it is “AddPostCondition”. By that, you can easily differentiate already in the list of changes.
3. Create Validations
3.1 Create a rule and assign to Validation
This video explain how you can create a rule and use it a validation. The example here is to check if either email or a phone is provided in the contact details and if not the save would fail with an error.
3.2 Deactivate validation
Next you can check how to deactivate the validation, so it does not apply anymore.
Note: The rules and validation you create are at the UI component level. Hence unlike HTML5 client, you need to navigate to the UI component level and then create the rule and/or validations. The rules are reusable with the UI component it’s been created in. This means you can assign the same rule to properties of multiple fields on the same screen.
4. Create and Assign Page Layouts
This video shows how to create new page layouts and assign the page layouts to user’s role. The page layouts are rendered based on the user’s role as well as certain field values on transactions. The case here is showing simple and cleaner screens while the opportunity is in certain stage, and as the stage increases more fields and tabs appear – some of those fields are mandatory fields.
This is the end of part 2 of the blog. In the part 3, there are more such videos and how-to for other capabilities of adaption in Fiori client.
How do you change a KUT field label for a field created in HTML?
I think it possible only via Language Adaptation
From upgrade v2005 you can change field label via KUT
Is it possible to use these rules to determine Dates like End Date using logics as current date + 30 days?
Is it possible to remove EDIT button with a rule if the Account or Contact has status of Obsolete? I'm not finding any way to do this.
I did not found how to remove EDIT button. But you can use the workaround.
1. Create rule like this https://i.imgur.com/QBRVY4e.png
2. Set this rule to ALL Fields
I have the next result.
Status “Active” – all fields are editable (standard case).
Status “Obsolete” – fields with the rule aren’t editable for users
Great content! Congrats on this blog post, keep up the good work!
I have a question, though: after creating a property rule for a field, like visibility based on something, how can I manage to import it in the production tenant? I can't find the adaptation change ID on transport management.
Can anyone help me on this one?