...
Ep4. Managing a developer Code List
This feature is not quite ready yet.
Ep5. Managing End User Core Component and Localized BIE Extension
The purpose of EUCC is to extend the standard and to be used in BIEs.
Explain that End User Core Component (EUCC) is not like Developer/Standard Core Component. It has three states like BIE - WIP, QA, and Production.
However, unlike BIE, EUCC can shuttle from Production back to WIP but only backwardly compatible changes can be made.
Create two EUBCCPs, say EUBCCP1 and EUBCCP2. Move EUBCCP1 to QA.
Create two EUACCs, say EUACC1 and EUACC2. Each EUACC uses each EUBCCP created earlier and some other standard BCCPs. Point out that just like developer CC, relationship can be created with EUCC in any state.
Create two EUASCCPs, say EUASCCP1 and EUASCCP2, from the EUACC1 and EUACC2, respectively. Add EUASCCP2 to EUACC1.
Point out that OAGIS extension cannot be created.
Create a BIE. Point out the a BIE cannot be created directly on an EUASCCP.
Check some boxes in the BIE and invoke a Localized BIE Extension.
Add EUASCCP1 and EUBCCP1, a standard ASCCP, and a standard BCCP to the extension. Point out that EUCC in any state can be used.
Move the User Extension Group ACC to Production.
Go back to the BIE, point out EUASCCP1 and EUBCCP1 cannot be enabled.
Move the EUASCCP1 and EUBCCP1 and EUBCCP2 to Production.
Go back to the BIE, show that some part of the EUASCCP1 can now be enabled and customized. However, EUASCCP2 is still locked.
Take ACC1 back to WIP.
Go back to BIE, shows that EUASCCP1 is locked again.
Go to EUACC1 and add a standard BCCP and move all the EUCC to Production.
Show that every part of the extension can now be customized.
Ep6. End User Core Component and BIE Extension
...