jolly
VIP Member
Hi all,
My client is looking at using UDOs where possible in their 9.2 upgrade, to eliminate modifications to custom JDE objects. We've identified a number of patterns and ways to use UDOs to eliminate them so that's all looking well and good.
Now we're looking at how we manage these UDOs. All the UDOs for the upgrade will be designed and built by the developers as e they are working their way through the modified object list, retrofitting modifications that can't be replaced by UDOs. I expect they will do this in DV and request to share when ready. Someone will be tasked with a quick sanity check before sharing and promoting into PY for testing and approval.
Does this make sense so far?
I think initially when 9.2 goes live, UDOs will still be designed and built within the IT department to keep the application look standardised, so business users outside IT would have VIEW security for UDOs but no access to create/publish/modify UDOs.
Also, we would like to lock in certain UDOs such as queries and personal forms (but not layouts) so the users can't change selection of those at runtime. Is that possible? Where a personal form or query has been set against a form, we want to ensure the end users are going to work with that UDO in effect.
Thanks in advance for any suggestions and corrections!
My client is looking at using UDOs where possible in their 9.2 upgrade, to eliminate modifications to custom JDE objects. We've identified a number of patterns and ways to use UDOs to eliminate them so that's all looking well and good.
Now we're looking at how we manage these UDOs. All the UDOs for the upgrade will be designed and built by the developers as e they are working their way through the modified object list, retrofitting modifications that can't be replaced by UDOs. I expect they will do this in DV and request to share when ready. Someone will be tasked with a quick sanity check before sharing and promoting into PY for testing and approval.
Does this make sense so far?
I think initially when 9.2 goes live, UDOs will still be designed and built within the IT department to keep the application look standardised, so business users outside IT would have VIEW security for UDOs but no access to create/publish/modify UDOs.
Also, we would like to lock in certain UDOs such as queries and personal forms (but not layouts) so the users can't change selection of those at runtime. Is that possible? Where a personal form or query has been set against a form, we want to ensure the end users are going to work with that UDO in effect.
Thanks in advance for any suggestions and corrections!