Applies to:

Siebel CRM - Version 8.1.1.14.3 [IP2014] and laterInformation in this document applies to any platform.

Goal

We require two internal Organisations within our Siebel environment to have access to modify their own Activity Templates. We enabled this, using standard Organisation visibility, as follows:

1. On the "Activity Template" BC, add a new field called "Organization Id", based on the existing BU_ID column2. Add a Join to S_BU, using the new field3. Add a new field called "Organization", based on the join, exposing the NAME column from S_BU4. Add a picklist to the new field (LS Organization PickList)5. Add a new "Organization" Bus Comp View Mode to the BC, using the new "Organization Id" as Visibility Field6. Expose the new field on the "Activity Template List Applet" applet7 Change the View Mode on the "Activity Templates Administration View" to "Organization"8. Compile9. Log in as SAMIN10. Using the new UI columns, change an existing Activity Template BU from "Default Organization" to something else11. Navigate to the vanilla "PUB GOV Case Activity Plans View"12. Locate a Case record in the top applet13. Create a record in the Activity Templates applet14. Step off the record15. Note that NO activity records are created16. Repeat steps 8 to 14, setting the Activity Template back to "Default Organization"17. Note that activity records ARE created when the Activty Template is applied

We really want to use OOTB visibility to control access to these records, but we also want our user and system processes, related to Activity Templates, to continue working.