cancel
Showing results for 
Search instead for 
Did you mean: 

UWL Customization (Custom Config and iView Correlation)

Former Member
0 Kudos

Hi,

Requesting validation/inputs of below 2 points -

1 - Assumption is that standard UWL functionality stays AS-IS, if we customize using custom UWL iViews (delta link copies of standard UWL PCD content) and custom config UWL XMLs.

2 - How does the different custom UWL iViews link to different custom Config XMLs? (eg mdm_custom.xml or uwl.custom_navigation.xml or uwl.webflow.custom_SAP_SRM_Workflow or uwl.webflow.custom_SAP_ECC_Workflow)

We dont define this anywhere - how does the system pick this up?

I read several documentation & blogs, but was not able to decipher the XML to PCD Content correlation in case of custom.

BR.

Accepted Solutions (0)

Answers (1)

Answers (1)

chintan_virani
Active Contributor
0 Kudos

There is only one iView --> UWL iView.

Now when you define systems and register the system with proper connector it automatically creates the appropriate XML which contains all itemts to be fetched from backend. So if you have an MDM system as well SRM system, you need to create two system and create appropriate connections through UWL administration.

Your mdm.xml will contains items from MDM and srm.xml will contain items from SRM and so on. These items are related to Task/ItemTypes from respective backend. Say TS0001 is from MDM and TS99999 is from SRM.

If there is any conflict for tasks it will pick the XML with Higher Priority.

And now in your "UWL iView" you can access both the tasks.

Former Member
0 Kudos

Thanks Chintan,

Okay. This is what I could infer -

In all cases its only one iView (com.sap.netweaver.bc.uwl.uwl_iview).

But XML's can be any number eg mdm.xml (standard - already in system), mdm_custom.xml (with customizations), based on higher priority it will be applied.

So coming back to my question -

So does that mean, once custom xml (mdm_custom.xml) is applied with higher priority, it will take effect in both standard and custom iviews (delta link of standard UWL iview and some iview properties changed)?

chintan_virani
Active Contributor
0 Kudos

Yes. But ideally after you make a change in XML i.e update the custom XML with Higher Priority then make sure you clear the UWL cache as well from UWL Administration.

Former Member
0 Kudos

Hi Chintan,

Thanks for the fast response.

Q1 - Is there any work around, where standard functionality can be retained and only custom xml should apply to custom iview? This is because, we have functional team working on standard and technical that needs to work on custom concurrently and we dont want custom to have any impact on standard?

Q2 - Is it possible to have different set of action buttons for different roles - eg Custom Role (SRM Approver) should see certain buttons only - eg Approve, Reject,Edit,Close, Print Preview etc and Admin should get all standard buttons. Is this to be done at WF level or part of UWL Customization? Any hints.

BR,

Dhanz