Resultmaker Solution Design - PowerPoint PPT Presentation

1 / 30
About This Presentation
Title:

Resultmaker Solution Design

Description:

In OCMS create a reference to the script on the step(s) where it should execute ... Advanced client functions, including show/hide related to the data model if ... – PowerPoint PPT presentation

Number of Views:46
Avg rating:3.0/5.0
Slides: 31
Provided by: akaaren
Category:

less

Transcript and Presenter's Notes

Title: Resultmaker Solution Design


1
Resultmaker Solution Design
2
Overview
3
Components, tools, content elements
4
Simple process design
5
Simple process design
Online Consultant (OC) Back End
OC Front End
OC Questionnaire Engine
OC Broker
Transaction Pre- Processor
Other Systems
OC Workflow Engine
Other Systems
Run-time
Online Consultant Management Suite (OCMS)
Design-time
XML Factory Client
Questionnaire Designer
Workflow Designer
Broker Tools
Form Data Editor
Script Editor
Content auto-generation
XML Factory
External Process Data Source (not a part of
standard Enterprise Platform)
Form Export

OC Export
Data Model Tool
Taxonomy Tool or database
XML Schema Generator
External XSD repository
6
Simple process design
7
Process is designed as a Process Matrix


8
Broker rules enable a non-developer to manage
back-office integration
9
Common data model underneath process
10
Common data model underneath process
Online Consultant (OC) Back End
OC Front End
OC Questionnaire Engine
OC Broker
Transaction Pre- Processor
Other Systems
OC Workflow Engine
Other Systems
Run-time
Online Consultant Management Suite (OCMS)
Design-time
XML Factory Client
Questionnaire Designer
Workflow Designer
Broker Tools
Form Data Editor
Script Editor
Content auto-generation
XML Factory
External Process Data Source (not a part of
standard Enterprise Platform)
Form Export

OC Export
Data Model Tool
Taxonomy Tool or database
XML Schema Generator
External XSD repository
11
Common data model underneath process
12
XML Factory enables a closed loop design of
data model and forms and system integration
13
Scripting, server side
14
Scripting, server side
Online Consultant (OC) Back End
OC Front End
OC Questionnaire Engine
OC Broker
Transaction Pre- Processor
Other Systems
OC Workflow Engine
Other Systems
Run-time
Online Consultant Management Suite (OCMS)
Design-time
XML Factory Client
Questionnaire Designer
Workflow Designer
Broker Tools
Form Data Editor
Script Editor
Content auto-generation
XML Factory
External Process Data Source (not a part of
standard Enterprise Platform)
Form Export

OC Export
Data Model Tool
Taxonomy Tool or database
XML Schema Generator
External XSD repository
15
Scripting, server side
16
Scripts have access to data and objects and
enables a developer to extend the OC infinitely
17
Scripting, client side
18
Scripting, client side
Online Consultant (OC) Back End
OC Front End
OC Questionnaire Engine
OC Broker
Transaction Pre- Processor
Other Systems
OC Workflow Engine
Other Systems
Run-time
Online Consultant Management Suite (OCMS)
Design-time
XML Factory Client
Questionnaire Designer
Workflow Designer
Broker Tools
Form Data Editor
Script Editor
Content auto-generation
XML Factory
External Process Data Source (not a part of
standard Enterprise Platform)
Form Export

OC Export
Data Model Tool
Taxonomy Tool or database
XML Schema Generator
External XSD repository
19
Scripting, client side
20
Generation of content from external sources
21
Generation of content from external sources
(incl. import of processes)
Online Consultant (OC) Back End
OC Front End
OC Questionnaire Engine
OC Broker
Transaction Pre- Processor
Other Systems
OC Workflow Engine
Other Systems
Run-time
Online Consultant Management Suite (OCMS)
Design-time
XML Factory Client
Questionnaire Designer
Workflow Designer
Broker Tools
Form Data Editor
Script Editor
Content auto-generation
XML Factory
External Process Data Source (not a part of
standard Enterprise Platform)
Form Export

OC Export
Data Model Tool
Taxonomy Tool or database
XML Schema Generator
External XSD repository
22
Generation of content from external sources
(incl. import of processes)
23
Pure model driven approach is supported, where
the process is generated from data
24
Complex workflow designs held as data now are
generated straight from the source
25
Process as data
  • (1) Activities and their grouping in sup
    processes (phases) in a repository structure
    such that an activity (a node) can be a part of
    several phases (tree structures) by reference,
    so that when the activity definition is updated,
    it will have effect in all the phases / processes
    that have this activity in them
  • (2) Roles (and behind them which users have which
    roles each user may have several roles, adding
    up the access rights of each role like in Active
    Directory)
  • (3) Relations between roles and activities,
    phases etc. access rights (execute, read,
    deny)
  • (4) Process transaction data model from elements
    and data types through groups of elements to
    interfaces (the highest level of groups)
  • (5) An activity often makes reference to a form
    and a form is an implementation of a data model
    for an interface. So we must have
  • a tree structure of data model, repository style,
    such that the forms are the top elements, and
    they are broken down into groups and elements
    like activities, an element and a group can be
    part of several groups
  • a relationship between forms and activities
  • (6) Process transaction data model from elements
    and data types through groups of elements to
    interfaces (the highest level of groups)
  • (7) Relationships between activities (and between
    groups af activities) (the main relationships
    between two activities are sequence constraints
    or predecessors as are known from the Gantt
    model but also logical relationships exist,
    which means that the data of one activity will
    change, if the data of another activity changes)
  • (8) Relationship between enumerations of an
    element ( drop down values of a form) and
    groups of elements such that we can implement
    conditionally required questions in a form, i.e.
    parts of a form that appear if a certain answer
    to a dropdown / radio button is selected, and
    disappear if not selected. These will be
    implemented as client side logic in the form
    (e.g. JavaScript in eForms).
  • (9) Variant information on activities and phases
    Under which condition is an activity active (e.g.
    if an amount applied for is above 20,000 then a
    certain approval is required, otherwise it is not
    required (and absent from the process))
  • (10) Systems that hold the data and receive the
    data when created by the process

26
Deployment management and advanced solution
management
27
Deployment management of processes on multiple
platforms
28
Keeping all content elements in sync on multiple
platforms
Dev
Integr
Test
Stage
Prod
29
Deployment management of data model, XML Schemas

30
Advanced solution management
Write a Comment
User Comments (0)
About PowerShow.com