Ep1. Creating and Revising Standard Core Components Basic
Scenario
Introduced Developer role.
Need to revise Document Reference to add URL/URI and Title.
Lock in as oagis.
Search for Document Reference ACC using filter.
Use ACC filter and DEN sorting to open Document Reference.
Click on Revise. Point out that a developer can revised any published CCs on working branch. The developer would take over the ownership.
However, determined that Document Identification Base ACC needs to be revised instead.
Click on Open in new Tab.
Cancel the revision on the Document Reference.
Go back to Document Identification Base ACC to click on Revise.
Click on append Property Last.
Search for the URI BCCP to add. Fill in Definition Source http://www.openapplications.org/oagis/10 and Definition.
Click on append Property Last.
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.
Open Document Reference again to show that the URI and Title fields are there. Emphasize the use of double quote.
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.
Set base of Statement Context to Identification.
Add Document Reference to Statement Context. Filter with ASCCP.
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.
Create Statement Context ACC.
Set based ACC to Statement Context Base ACC.
Invoke Create OAGi Extension.
Create Statement Context ASCCP.
Log in as sermdev in another window.
Create Statement Base ACC. Set based ACC to Identification. Set Component Type to Base.
Append Free Form Text Group.
Append Statement Context ASCCP. Point out that you can use CC created by another user.
Demonstrate moving the association order. Move Statement Context to before Free Form Text Group.
Create Statement. Set based ACC to Statement Base ACC.
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.
End of Demo.
Ep2. Create a standard OAGi BOD
Continued from Ep1.
Log in as oagis developer user.
Create Substance Declaration Header Base ACC. Set based Type to Header Base.
Add Party ASCCP to it.
Need to add Statement ASCCP. Decide to add to Party Base. Open Party Base in a new tab.
Try to add Statement ASCCP. But didn’t have it.
Open CC View/Edit on another tab. Saw that Statement ACC is already there but not ASCCP.
Create a new Statement ASCCP.
Go back to the Party Base tab. Search for Statement ASCCP again. It shows up now and can be added.
Close Party Base tab.
Go back to Substance Declaration Header Base tab. Refresh. Click Expand All.
Expand Party to shows that Statement was added.
Create substance Declaration Header ACC. Set Substance Declaration Header Base as based ACC.
Invoke Create OAGi Extension Creation.
Create Substance Declaration Header ASCCP.
Create Substance Declaration ACC Noun. Add Substance Declaration Header and Item Master as properties.
Invoke Create OAGi Extension
Go back to CC page. Invoke Create OAGi BOD.
Ep3. Collaborative CC development
Show CC development. Emphasizing the Commenting feature.