Hi , A small addition to the above:
- A Chevron Workflow could have one or more layouts - The layout details need not be stored with the Workflow instance Thank You, Sameera On Wed, Nov 12, 2014 at 5:20 PM, Himasha Guruge <[email protected]> wrote: > Hi Chathura, > > After the meeting with Sameera, he suggested the following design model. > > Since every sub chevron element itself also represents a > process,suggestion was to create two asset types named chevron and chevron > workflow. > > 1.chevron.rxt : Includes all metadata > fields.(Name,Version,Provider,Predecessor,Successor,Process model) > > 2. chevron workflow.rxt: Includes following two fields. > > 2.1 *sequence*: This will hold all chevron ids that we draw on the > canvas. > > 2.2* layout:* This will hold the formatting data of chevron element > drawn on the canvas. Such as chevron id, positionX,positionY. > > Views for these 2 asset types will be as follows. Please refer [1]. > > 3.Create page for chevron asset type : User can enter metadata fields > listed, and on click of create button those values will be added to > chevron.rxt. > > 4. Create page for chevron workflow asset type: User can drag and drop > chevron icon can create their diagram. On click of create button, ids of > the chevron icons will be saved under sequence field, layout details in > layout field. An association will be made between the relevant chevron > asset and chevron asset workflow. > > 5. Chevron view page : Chevron related data (name, version etc) will be > loaded in a table while the associated diagram will be loaded in a canvas. > > The only catch is that all diagram related data ( layout and sequence) > will be saved in JSON format. Therefore no xml will be included. Are there > any restrictions such as the diagram should be maintained in xml format? > Please provide your feedback on this design suggestion. > > Please refer [1] for further reference. I will continue working on the > previous design model(with one asset type) until a decision is made. > > [1].chevron diagram editor design suggestion > <https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTWZUU1g5X3RyRzA/view?usp=sharing> > > > > > Chevron diagram editor design suggestion.jpg > <https://docs.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTWZUU1g5X3RyRzA/edit?usp=drive_web> > > Thanks & Regards, > > Himasha Guruge > *Software Engineer* > WS*O2* *Inc.* > Mobile: +94 777459299 > [email protected] > -- Sameera Medagammaddegedara Software Engineer Contact: Email: [email protected] Mobile: + 94 077 255 3005
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
