Ep1. Creating and Revising Standard Core Components Basic

Scenario

1. Introduced Developer role.

2. Need to revise Document Reference to add URL/URI and Title.

3. Lock in as oagis.

4. Search for Document Reference ACC using filter.

5. Use ACC filter and DEN sorting to open Document Reference.

6. Click on Revise. Point out that a developer can revised any published CCs on working branch. The developer would take over the ownership.

7. However, determined that Document Identification Base ACC needs to be revised instead.

8. Click on Open in new Tab.

9. Cancel the revision on the Document Reference.

10. Go back to Document Identification Base ACC to click on Revise.

11. Click on append Property Last.

12. Search for the URI BCCP to add. Fill in Definition Source http://www.openapplications.org/oagis/10 and Definition.

13. Click on append Property Last.

14. Search for the Title BCCP to add. Fill in Definition Source http://www.openapplications.org/oagis/10 and Definition. Point out that default cardinality is 0..n. If you need to change the max or min, you can do it. Change it to 1. And change to unbounded again demonstrating that you can type in -1 or unbounded.

15. Open Document Reference again to show that the URI and Title fields are there. Emphasize the use of double quote.

16. Create Statement Context Base ACC. Set component type to Base. Point out that when Base is selected Abstract is selected by default. There will be a naming rule implemented later.

17. Set base of Statement Context to Identification.

18. Add Document Reference to Statement Context. Filter with ASCCP.

19. Add Contract Reference to Statement Context. Search “Contract Reference”. Show that clicking on the blank space shows the definition. Show that clicking on the name open up the ASCCP in a new tab for detail inspection.

20. Create Statement Context ACC.

21. Set based ACC to Statement Context Base ACC.

22. Invoke Create OAGi Extension.

23. Create Statement Context ASCCP.

24. Log in as sermdev in another window.

25. Create Statement Base ACC. Set based ACC to Identification. Set Component Type to Base.

26. Append Free Form Text Group.

27. Append Statement Context ASCCP. Point out that you can use CC created by another user.

28. Demonstrate moving the association order. Move Statement Context to before Free Form Text Group.

29. Create Statement. Set based ACC to Statement Base ACC.

30. Invoke Create OAGi Extension. Walk through the entities got generated. Point out that Extension is not reusable b/c it is a local element. The name is not unique. Only some properties of Extension components can be edited.

31. End of Demo.

Ep2. Create a standard OAGi BOD

Continued from Ep1.

1. Log in as oagis developer user.

2. Create Substance Declaration Header Base ACC. Set based Type to Header Base.

3. Add Party ASCCP to it.

4. Need to add Statement ASCCP.

5. Create substance Declaration Header ACC. Set Substance Declaration Header Base as based ACC.

6. Invoke Create OAGi Extension Creation.

7. Create Substance Declaration Header ASCCP.

8. Create Substance Declaration Base ACC . Add Substance Declaration Header and Item Master as properties.

9. Create Substance Declaration ACC. Set based ACC to Substance Declaration Base ACC. Invoke Create OAGi Extension

10. Go back to CC page. Invoke Create OAGi BOD.

Ep3. Managing a CC release

Prepare some new and revised CC. Some even though should be in the release are still in WIP or Draft state. Some don’t want in the release that are in WIP, Draft, Candidate, or Deleted state.

1. Explain that a release has 3 states - Initialized, Release Draft, and Published.

2. Log in as a developer user - sermdev.

3. Create a new release.

4. Point out that it is in the Initialized state.

5. Create another release. Point out that there can be multiple releases in the initialized state. But there can be only one release in Release Draft or Published state. Multiple initialized releases are allowed for planning purpose.

6. Release in the Initialized state has no content yet, so it won’t appear on the list of branches of the CC. Go to CC View/Edit page and show that no branches for the releases in the Initialized state.

7. Go back to release page and create a Draft.

8. Assign content to the release. You may choose not to assign some content to the release because it is for a future release or you simply don’t want it, e.g., in Deleted state.

9. Run validation. Show invalidity, like there is a necessary ASCCP in WIP state that is not included.

10. Fix the issue. Validate again.

11. Create the draft release.

12. Show that the draft release now appears on the CC View/Edit page for viewing and reviewing only.

13. At this point people can be invited to review the release and give comments.

14. Point out that more CCs can be added or changed in the Working branch.

15. If all reviews have been gathered and changes need be made to the release draft, the release needs to be taken back to Initialized. Revert to initialized.

16. Now you can go back and add a property to an ACC by taking it back to the WIP state.

17. Create the release draft again. This time published it.

18. Show that now there is the Published release branch on the CC View/Edit page.

19. The end.

Ep4. Managing a developer Code List

Ep5. Managing End User Core Component

Ep6. End User Core Component and BIE Extension

Ep7. Collaborative CC development

Show CC development. Emphasizing the Commenting feature. Transfer ownership. Talk more about states. Talk about Deleted CCs.