What's new — Designer Studio Proj 585 Dharma Initiative Lisa

Set attributes of a sub-flow (or sub-process) and Spin-off shapes through property panels.

https://www.chordiant.net/docs/DOC-14980

Create new Process Modeler - editing spinoff shape properties

Create new Process Modeler - Editing flow properties

Shape labels - ability to change without opening property panel

A Design Framework for the Modeler Canvas – PROJ-585
https://www.chordiant.net/docs/DOC-15226

Decision "Property Panel" Section - ability to set decision shape attributes using properties panel. Following shows sample for assignment

Flow rule - Process Modeler - Decision shape

https://www.chordiant.net/docs/DOC-14980

Flow shape properties - view in non-modal so that other objects can be selected and focus can change when viewing properties.

A Design Framework for the Modeler Canvas

https://www.chordiant.net/docs/DOC-15226, slides 7,8,16,17

Connectors - status prompting. SmartPrompt on Status field in Transition Property Panel.

-status retrieved from 'From' shape

Draft Mode - icon will toggle on/off

Integrator shape - ability to set attributes via browser

https://www.chordiant.net/docs/DOC-14980

Process Discovery Map view -(GRP-24004)View flow using the Process Discovery Map view to visualize process in the same way that flows are represented in the App Profile. https://www.chordiant.net/docs/DOC-15368

• Implement a View mode in the toolbar and add a Discovery Map option. Use existing code to display
• Ability to identify current view at a glance (icon?)
• Toolbar disabled for this and any view other than modeler.
  

Update many:

DCO: Creating Discovery Maps

SplitforEach-(GRP-22603) -ability to set attributes via property panel in browser. https://www.chordiant.net/docs/DOC-14980

• function as in Visio
• property panel to include dynamic behavior, layouts, styling, localization and multi-browser support

Process Modeler - Editing End shape

Process Modeler - Editing Assignment Service Shapes (draft 2/10)

Switching views between Mxgraph and Visio -(GRP-23844) be able to switch easily between the 2 tools.

• Be able to open and edit drawing in one tool that was created in the other.
• Determine how best to launch.
  

Will require either new, or updates multiples places.

Story incomplete 2/10 - moved to next sprint  

Assignment Service Shape-(GRP-22607) -ability to set attributes via property panel in browser. https://www.chordiant.net/docs/DOC-14980

• function as in Visio
• property panel to include dynamic behavior, layouts, styling, localization and multi-browser support

Ticket shape (GRP-22608)- -ability to set attributes via property panel in browser. https://www.chordiant.net/docs/DOC-14980

• function as in Visio
• property panel to include dynamic behavior, layouts, styling, localization and multi-browser support
• Ticket shall have the same property panel as it does in Visio today OR, if possible, be implemented as an additional property in all of the other shapes so that it acts and displays as a modifier and not something that has its own panel (the underlying data structure would have to remain the same).

This is no longer a separate shape, but is a tab under many other shapes:

• Assignment (draft 2/9)
• Assignment-Service (draft 2/10)
• Decision (draft 2/9)
• End (draft 2/14)
• Integrator
• Spinoff
• Split-Join
• Split-ForEach 3/1/11
• Subprocess
• Utility

Crossover from Visio to Mxgraph -(GRP-23844) be able to switch easily between the 2 tools.

• Open/edit Visio flow in MxGraph.
• Save Visio to MxGraph. Can't go back.
• New flow - button for Edit in Visio

Split -join using single shape with subflow references-(GRP-25388) - to implement split-join behavior without requiring the visual representation of each subprocess inside the split-join shape, so we can get the functionality even though the visual aspects don't quite match what was previously available in Visio.

• There is a new shape to represent the Split-Join (BPMN parallel task).
• A single shape represents the Split-join. The shape’s property panel will have a repeating list of subprocesses and use the same data structure for listing those subprocesses as the Visio implementation.

Implement Ticket, Notify, SLA, Spin-off as modifiers to shapes that are nodes in the graph (GRP-23936)- Split-ForEach & Split-Join will also be treated as modifiers, though they will appear on the stencil as their own independent shapes.

• Ticket shall be represented as a BPMN intermediate event (like the BPMN visio stencil) with a solid triangle in the middle (BPMN signal).
• SLA shall be represented as BPMN intermediate timer event.
• Notify shall be represented as BPMN "Receive Task" (envelope icon).
• Spinoff will be represented using a "tornado" icon in the rectangular shape.
• Split-ForEach will be represented using a BPMN "loop" marker in the rectangular shape.
• Split-Join will be represented using a BPMN "Parallel" marker in the rectangular shape.

Display flow image (jpg) for flows edited in Visio (GRP-26779)

• support view overlays
• support left/right/double-click actions

Revisit Property Panels for consistency -(GRP-26774)

https://mesh.pega.com/docs/DOC-14980 - property panels for each shape laid out in a consistent, easy-to-use layout (that is in line with the panels used in the UI designer for sections/harnesses)

Set larger-scale default grid based shape sizes -(GRP-23850) - ability to easily drag elements in MxGraph within a larger grid scale, so that it is easier to get the elements in the flow to be aligned properly.

• The default grid scale should be adjusted so that it is equivalent to the spacing between connector points. Start, End, and Decision shapes may need to be resized to be an even ratio of the larger shapes to make sure all connection points will line up.
• Automatically snap to grid on add (and move) of shapes from right-click or drag & drop.

Upgrade version of MxGraph (GRP-27438)-

none

Display flow image (jpg) for flows edited in Visio (GRP-26779-1) - Carried over from last sprint

• support view overlays
• support left/right/double-click actions

Switching views between MxGraph and Visio (GRP-23844-2)- Carried forward from sprint 7 and 8 -to be able to take a Visio flow and edit in MxGraph or continue to edit in Visio.

Preferred method is to pull in form-based "pieces" that we need into the harness-based version in order to be able to launch Visio.

Flows should render "reasonably" when switching from Visio to MxGraph.

• Ability to open and edit a drawing that originated in Visio in MxGraph (assuming copied Rule-Obj-Flow to Rule-Obj-Flow-HarnessedBased).
• Once a change is made in MxGraph view and save it, the access to Visio is denied.
• You can still edit in Visio [until you cross over].
• When a flow is saved in MxGraph, the user is warned about closing the door to Visio.

Ged rid of Rule-Obj-Flow (harness-based) rule type (GRP-25985)- ability to open, view, and edit, in MxGraph, a flow that was created/last updated in Visio (no more Rule-Obj-Flow-Harnessbased).
Flow layout should mirror that of the Visio diagram (the shapes are more important than the connectors).

Make sure connections render in a reasonable manner (this could involve ignore existing connector points).

• Rule-Obj-Flow rule form is harness based.
• Existing Visio flows should still work.
• MxGraph editor will not impact unrecognized types in data model.
• Should be available on SDE for some people (not everyone) to use.

none