Procesy5 documentation glossary

Procesy5 System Framework

Procesy5 most important registry components

ROOT_INSTALL_DIR

schemaProcesy5 Important Registry Component
ant-object
ant-object
ant-object contains Data Business Objects Modules which can be on Data Business Object Installed Stateor Data Business Object Not Installed State
static
p5WFS
GetFeature.js
Library/example for creating customized USER intefaces for API GetFeature.js

PROCESY5_INSTALLED_DOMAIN

This is licence parameter. Every system is licenced for single domain e.g. biuro.biall-net.pl

Procesy5 Process (BPMN) Database

Association By Business Object
If Modelling Business Objects was done to Business Objects Definitions, they exists in Procesy5 Business Object Templates Repository. After applying Business Objects Transformations Component they are transfrerred to Procesy5 SimpleSchema component and can be then be done Association By Business Object via Procesy5 Process and Resources Modeller
Note: It is currently work in progress
Note: To propeorly work this method it is required to correctly bind Namespace to Procesy5 storage database as discussed in there

Procesy5 Business Object Templates Repository

Busines Objects Dependency Analysis Repository for Business Objects Transformations Component

Constructed ComplexType Repository
Transport Map Repository
Simplified Transport Map Repository
By analysis of Transport Map Repository it create Simplified Transport Map Repository which contains:
  1. Root element RelatedFeature
    1. with attributes
      1. xpath="ID" means that this is key Primary xs:unique
      2. if used in Namespace Binding Data Business Object to Local Storage it can be bypassed by Primary Key Handling in Data Business Objecs binded to Local Storage
      3. typeName="p5_default_db:PROCES" means to query this Root Schema Element from Business Data Object
      4. typeNameRealResource="p5_default_db:CRM_PROCES" means that this is Root Schema Element of typeRoot ComplexType, according to default_db objects which are intend to be instanded in default database.
        Example:
        <RelatedFeature xmlns:p5_tr_map="http://biuro.biall-net.pl/xmlschema_procesy5/default_db_xml_cache/procesy5_translate_map.xsd"
                xmlns:system_cache__appinfo="http://biuro.biall-net.pl/xmlschema_procesy5/default_db_xml_cache/appinfo.xsd"
                xmlns:hfp="http://www.w3.org/2001/XMLSchema-hasFacetAndProperty"
                xmlns:default_db="http://biuro.biall-net.pl/xmlschema_procesy5/default_db"
                xmlns:p5_default_db="https://biuro.biall-net.pl/wfs/default_db"
                xmlns:ogc="http://www.opengis.net/ogc"
                xpath="ID"
                typeName="p5_default_db:PROCES"
                typeNameRealResource="p5_default_db:CRM_PROCES"
                xml_id="d3e1">
  2. simpleTypeMakeOgcFilter element with easy to implement in Procesy5 interfaces GUI Development or especially for Namespace Binding Data Business Object to Remote Foreign Storage to simulate Instance.

    It allows to Incorrect Instance detection in Procesy5 Local Storage database.

    Example: 
    <simpleTypeMakeOgcFilter name="PROCES">
      <ogc:Or>
         <ogc:PropertyIsEqualTo>
            <ogc:PropertyName>TYPE</ogc:PropertyName>
            <ogc:Literal>PROCES</ogc:Literal>
         </ogc:PropertyIsEqualTo>
      </ogc:Or>
</simpleTypeMakeOgcFilter>
  3. Root Schema Element from Business Data Object to be retrieved, example:
     <p5_default_db:PROCES xpath="CRM_PROCES"
                         xml_id="d3e5"
                         system_cache__appinfo:id="_CRM_PROCES___d20e4507-1_CRM_PROCES">
      <ID xpath="ID" xml_id="d3e9"/>
      <PARENT_ID xpath="PARENT_ID" xml_id="d3e11"/>
      <path xpath="path" xml_id="d3e13"/>
      <DESC xpath="DESC" xml_id="d3e15"/>
      <TYPE xpath="TYPE" xml_id="d3e17"/>
  4. Child Related Features
    1. Relation information
      1. flat_relation_cache_xpath="default_db__x3A__CRM_PROCES:PROCES_INIT/PARENT_ID" - this is being evaluated for Namespace Binding Data Business Object to Remote Foreign Storage or can by bypassed for Namespace Binding to Storage by using Data Relation Handling subsystem.
    2. Not looped/recurenced
      1. example
        <RelatedFeature xml_id="d3e24"
                      typeNameRealResource="p5_default_db:CRM_PROCES"
                      typeName="p5_default_db:PROCES_INIT"
                      flat_relation_cache_xpath="default_db__x3A__CRM_PROCES:PROCES_INIT/PARENT_ID"
                      flat_relation_cache_name="ID"
                      system_cache__appinfo:get_default_db_obj_url_table_name="CRM_PROCES"
                      system_cache__appinfo:maxOccurs="0"
                      system_cache__appinfo:minOccurs="0"
                      system_cache__appinfo:id="_CRM_PROCES___d20e4521-1"
                      xpath="PARENT_ID"
                      xpath_value="../ID">
    3. Looped/Recurenced
      1. example
         <RelatedFeatureLoop xml_id="d3e19"
                          typeNameRealResource="p5_default_db:CRM_PROCES"
                          typeName="p5_default_db:PROCES"
                          flat_relation_cache_xpath="default_db__x3A__CRM_PROCES:PROCES/PARENT_ID"
                          flat_relation_cache_name="ID"
                          system_cache__appinfo:get_default_db_obj_url_table_name="CRM_PROCES"
                          system_cache__appinfo:loop_id="_CRM_PROCES___d20e4790-1_PROCES"
                          system_cache__appinfo:maxOccurs="unbounded"
                          system_cache__appinfo:minOccurs="0"
                          system_cache__appinfo:id="_CRM_PROCES___d20e4528-1"
                          xpath="PARENT_ID"
                          xpath_value="../ID">
Resources Dependency Analysis Repository
Stored in system_cache__resources_tree_generate_xsl_required_occurs_raport:detect_objects_parent_relations element

Procesy5 Features Matrix

Core Procesy5 System

Core Procesy5 element that are integrated together and communicate with each other its cababilites and documentation. This is documentation about.

Procesy5 server

Procesy5 server requirements

Ldap server requirements
We are mainly tested and using default in OSX Server LDAP integration wich is integrated with System API for:
  1. Authentication
  2. Groups managins
Note: Config file for this requirements is explained in Default LDAP connection config set
Http Web server requirements
We are tested with current version of https://httpd.apache.org mainly used from default OSX Server library for ease of components and distribution safety
Important libraries requirements
PHP library 5.2.0 or newer requirements
xslt saxon library requirements
JAVA
jdk + jre environment for mainly provide ant support and pdf outputs
Virtualisation informations
System is tested working on virtualized environment by minimal requirements of 4GB ram and 1TB of HDD storage recommended minimal
Internet Connection with correct DNS and Reverse DNS
Mainly reverse DNS is needed for CALDAV service and LDAP work correctly

Procesy5 ServerApplication

Procesy5 storage database

Procesy5 files storage

Procesy5 files storage repository

The main system storage is mostly default server

System API

Procesy5 system api is most important Core Procesy5 element element, which allows according to Adresses and versions of API and the base capabilities like:
  1. Data Structures Provider:
    1. List of possible tables and functions - GetCapabilities
    2. Table-Structure-DescribeFeatureType
    3. Structures with additional infos DescribeFeatureTypeAdvanced Polskie nazwy kolumn oraz informacje o uprawnieniach
    4. Structures of many tables - Multiple DescribeFeatureType Struktury wielu tabel
  2. Data provider:
    1. Data read GetFeature
    2. GetFeatureAdvanced additional informations about ACL
    3. GetFeature - Hits - returns number of rows matched in filters
      1. Filtering
        1. ogc:PropertyIsEqualTo
        2. ogc:PropertyIsLike
        3. ogc:PropertyIsNull
        4. ogc:Function
        5. ogc:IsLessThan, ogc:IsGreaterThen
  3. Data storage:
    1. Data Insert
    2. Data edit
    3. Modification of many records
    4. Data deletion

Procesy5 interfaces GUI Development

Procesy5 ordinary web interface

Procesy5 native Android Application

Procesy5 native iOS Application

Procesy5 native iOS Application
We have working application ready and aviable to download from AppStore

Business Objects Transformations Component

Business Objects Transformations Namespaces, Prefixes handling and modelling style

Namespace Binding to Storage
TargetNamespace and Prefix Binding Definition
TargetNamespace and Prefix Binding Definition
This example xmlns:default_db__x3A__CRM_PROCES="https://biuro.biall-net.pl/wfs/default_db/table/CRM_PROCES.xsd is using the following informations: xmlns:default_db__x3A__CRM_PROCES="https://biuro.biall-net.pl/wfs/default_db/table/CRM_PROCES.xsd
Namespace Database Storage Definition Prefix
default_db - this is Namespace Database Storage Definition. It means to bind to Procesy5 storage database (local storage)
Namespace Database and Instance Table string separator
__x3A__ - this is Namespace Database and Instance Table string separator
Namespace Object Instance Table Definition
CRM_PROCES - this is Namespace Object Instance Table Definition and it is expected to be main table name for instances for this object
Namespace Binding Data Business Object to Local Storage
Current System API provides Relation and Instances Derivation, which are described in Objects and Business objects
Namespace Binding Data Business Object to Remote Foreign Storage
Namespace Binding Data Business Object to Remote Foreign Storage type WFS
Note: to be specified
Namespace Binding Data Business Object to Remote Foreign Storage type XML File
Note: to be specified
Namespace Binding Data Business Object to Remote Foreign Storage type ODBC
This is expected to register custom API driver like ODBC to provide storage
Note: to be specified
default_db objects which are intend to be instanded in default database
In System API we use p5_default_db prefix with namespace binding to xmlns:p5_default_db="https://biuro.biall-net.pl/wfs/default_db" but for achieve better Modelling Business Objects strategy we use in modeling in table (Directory) (Transformations Component) we use such strategy:
  1. xmlns:default_db__x3A__CRM_PROCES="https://biuro.biall-net.pl/wfs/default_db/table/CRM_PROCES.xsd" we see: default_db ( __x3A__) CRM_PROCES
    1. default_db - means to add it to default_db (or p5_default_db)
    2. CRM_PROCES - means it is the correct instance table for object
Such Schema should contains objects like the following schema:
  1. Objects relations (import schema)
      <xs:import namespace="http://www.opengis.net/gml/3.2" schemaLocation="../Types/gml.xsd"/>
   <xs:import namespace="https://biuro.biall-net.pl/wfs/default_db/table/CRM_WSKAZNIK.xsd"
      schemaLocation="CRM_WSKAZNIK.xsd"/>
  2. simpleType definitions (filters)
    <xs:simpleType name="TYPE_Simple" id="_CRM_PROCES___d20e4484-1_TYPE_Simpl">
      <xs:restriction base="xs:string">
         <xs:enumeration value="PROCES_INIT"/>
         <xs:enumeration value="PROCES_GROUP_1"/>
         <xs:enumeration value="PROCES_GROUP_2"/>
         <xs:enumeration value="PROCES_BENEFIT_INFO"/>
         <xs:enumeration value="PROCES"/>
         <xs:enumeration value="TEXT_BREAK"/>
      </xs:restriction>
   </xs:simpleType>
   <xs:simpleType name="PROCES_INIT_Simple" id="_CRM_PROCES___d20e4492-1_PROCES_INI">
      <xs:restriction base="default_db__x3A__CRM_PROCES:TYPE_Simple">
         <xs:enumeration value="PROCES_INIT"/>
      </xs:restriction>
   </xs:simpleType>
   <xs:simpleType name="PROCES_Simple" id="_CRM_PROCES___d20e4495-1_PROCES_Sim">
      <xs:restriction base="default_db__x3A__CRM_PROCES:TYPE_Simple">
         <xs:enumeration value="PROCES"/>
      </xs:restriction>
   </xs:simpleType>
   <xs:simpleType name="PROCES_GROUP_1_Simple" id="_CRM_PROCES___d20e4498-1_PROCES_GRO">
      <xs:restriction base="default_db__x3A__CRM_PROCES:TYPE_Simple">
         <xs:enumeration value="PROCES_GROUP_1"/>
      </xs:restriction>
   </xs:simpleType>
   <xs:simpleType name="PROCES_GROUP_2_Simple" id="_CRM_PROCES___d20e4501-1_PROCES_GRO">
      <xs:restriction base="default_db__x3A__CRM_PROCES:TYPE_Simple">
         <xs:enumeration value="PROCES_GROUP_2"/>
      </xs:restriction>
   </xs:simpleType>
   <xs:simpleType name="PROCES_BENEFIT_INFO_Simple" id="_CRM_PROCES___d20e4504-1_PROCES_BEN">
      <xs:restriction base="default_db__x3A__CRM_PROCES:TYPE_Simple">
         <xs:enumeration value="PROCES_BENEFIT_INFO"/>
      </xs:restriction>
   </xs:simpleType>
  3. Base Object Model according to Database Structure/Table (Procesy5 storage database
    <xs:complexType name="CRM_PROCES" id="_CRM_PROCES___d20e4507-1_CRM_PROCES">
      <xs:sequence id="_CRM_PROCES___d20e4508-1">
         <xs:element name="ID" type="xs:int" id="_CRM_PROCES___d20e4509-1_ID"/>
         <xs:element name="PARENT_ID" type="xs:int" id="_CRM_PROCES___d20e4510-1_PARENT_ID">
            <xs:annotation>
               <xs:appinfo>
                  <system_cache__appinfo:flat_relation_cache>
                     <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:CRM_PROCES/ID"/>
                  </system_cache__appinfo:flat_relation_cache>
               </xs:appinfo>
               <xs:documentation>xpath="default_db__x3A__CRM_PROCES:CRM_PROCES/ID
               </xs:documentation>
            </xs:annotation>
         </xs:element>
         <xs:element name="path" type="xs:string" id="_CRM_PROCES___d20e4517-1_path"/>
         <xs:element name="DESC" type="xs:string" id="_CRM_PROCES___d20e4518-1_DESC"/>
         <xs:element name="TYPE" type="default_db__x3A__CRM_PROCES:TYPE_Simple"
            id="_CRM_PROCES___d20e4519-1_TYPE"/>
         
         <xs:element maxOccurs="unbounded" minOccurs="0" ref="default_db__x3A__CRM_PROCES:PROCES"
            id="_CRM_PROCES___d20e4528-1">
            <xs:annotation>
               <xs:appinfo>
                  <system_cache__appinfo:flat_relation_cache>
                     <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:PROCES/PARENT_ID"/>
                  </system_cache__appinfo:flat_relation_cache>
               </xs:appinfo>
               <xs:documentation>Tutaj nie dajemy appinfo relation cache - tylko w PARENT_ID do przetworzenia w celu odbudowania</xs:documentation>
            </xs:annotation>
         </xs:element>
         <xs:element maxOccurs="unbounded" minOccurs="0"
            ref="default_db__x3A__CRM_PROCES:PROCES_INIT" id="_CRM_PROCES___d20e4521-1">
            <xs:annotation>
               <xs:appinfo>
                  <system_cache__appinfo:flat_relation_cache>
                     <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:CRM_PROCES_INIT/PARENT_ID"/>
                  </system_cache__appinfo:flat_relation_cache>
               </xs:appinfo>
               <xs:documentation>Tutaj nie dajemy appinfo relation cache - tylko w PARENT_ID do przetworzenia w celu odbudowania</xs:documentation>
            </xs:annotation>
         </xs:element>
         <xs:element maxOccurs="unbounded" minOccurs="0"
            ref="default_db__x3A__CRM_PROCES:PROCES_GROUP_1" id="_CRM_PROCES___d20e4535-1">
            <xs:annotation>
               <xs:appinfo>
                  <system_cache__appinfo:flat_relation_cache>
                     <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:CRM_PROCES/PARENT_ID"/>
                  </system_cache__appinfo:flat_relation_cache>
               </xs:appinfo>
               <xs:documentation>Tutaj nie dajemy appinfo relation cache - tylko w PARENT_ID do przetworzenia w celu odbudowania</xs:documentation>
            </xs:annotation>
         </xs:element>
         <xs:element maxOccurs="unbounded" minOccurs="0"
            ref="default_db__x3A__CRM_PROCES:PROCES_GROUP_2" id="_CRM_PROCES___d20e4542-1">
            <xs:annotation>
               <xs:appinfo>
                  <system_cache__appinfo:flat_relation_cache>
                     <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:PROCES_GROUP_2/PARENT_ID"/>
                  </system_cache__appinfo:flat_relation_cache>
               </xs:appinfo>
               <xs:documentation>Tutaj nie dajemy appinfo relation cache - tylko w PARENT_ID do przetworzenia w celu odbudowania</xs:documentation>
            </xs:annotation>
         </xs:element>
         <xs:element maxOccurs="unbounded" minOccurs="0"
            ref="default_db__x3A__CRM_PROCES:PROCES_BENEFIT_INFO" id="_CRM_PROCES___d20e4549-1">
            <xs:annotation>
               <xs:appinfo>
                  <system_cache__appinfo:flat_relation_cache>
                     <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:PROCES_BENEFIT_INFO/PARENT_ID"/>
                  </system_cache__appinfo:flat_relation_cache>
               </xs:appinfo>
               <xs:documentation>Tutaj nie dajemy appinfo relation cache - tylko w PARENT_ID do przetworzenia w celu odbudowania</xs:documentation>
            </xs:annotation>
         </xs:element>
         <xs:element maxOccurs="unbounded" minOccurs="0"
            ref="default_db__x3A__CRM_WSKAZNIK:CRM_WSKAZNIK" id="_CRM_PROCES___d20e4557-1">
            <xs:annotation>
               <xs:appinfo>
                  <system_cache__appinfo:flat_relation_cache>
                     <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_WSKAZNIK:CRM_WSKAZNIK/ID_PROCES"/>
                  </system_cache__appinfo:flat_relation_cache>
               </xs:appinfo>
            </xs:annotation>
         </xs:element>
      </xs:sequence>
   </xs:complexType>
    and its default element
    <xs:element name="CRM_PROCES" type="default_db__x3A__CRM_PROCES:CRM_PROCES"
      id="_CRM_PROCES___d20e4562-1_CRM_PROCES"/>
Note: This is sample base object definition for making customized Modelling Business Objects
  1. You can model them in Derivation by restriction of ComplexType:
    <xs:complexType name="PROCES_INIT" id="_CRM_PROCES___d20e4565-1_PROCES_INI">
      <xs:complexContent id="_CRM_PROCES___d20e4566-1">
         <xs:restriction base="default_db__x3A__CRM_PROCES:CRM_PROCES">
            <xs:sequence id="_CRM_PROCES___d20e4568-1">
               <xs:element name="ID" type="xs:int" id="_CRM_PROCES___d20e4569-1_ID"/>
               <xs:element name="PARENT_ID" type="xs:int" id="_CRM_PROCES___d20e4570-1_PARENT_ID">
                  <xs:annotation>
                     <xs:appinfo>
                        <system_cache__appinfo:flat_relation_cache>
                           <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:CRM_PROCES/ID"/>
                        </system_cache__appinfo:flat_relation_cache>
                     </xs:appinfo>
                     <xs:documentation>xpath="default_db__x3A__CRM_PROCES:CRM_PROCES/ID
               </xs:documentation>
                  </xs:annotation>
               </xs:element>
               <xs:element name="path" type="xs:string" id="_CRM_PROCES___d20e4577-1_path"/>
               <xs:element name="DESC" type="xs:string" id="_CRM_PROCES___d20e4578-1_DESC"/>
               <xs:element name="TYPE" type="default_db__x3A__CRM_PROCES:PROCES_INIT_Simple"
                  id="_CRM_PROCES___d20e4579-1_TYPE"/>
               
               <xs:element maxOccurs="unbounded" minOccurs="0"
                  ref="default_db__x3A__CRM_PROCES:PROCES" id="_CRM_PROCES___d20e4588-1">
                  <xs:annotation>
                     <xs:appinfo>
                        <system_cache__appinfo:flat_relation_cache>
                           <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:PROCES/PARENT_ID"/>
                        </system_cache__appinfo:flat_relation_cache>
                     </xs:appinfo>
                     <xs:documentation>Tutaj nie dajemy appinfo relation cache - tylko w PARENT_ID do przetworzenia w celu odbudowania</xs:documentation>
                  </xs:annotation>
               </xs:element>
               <xs:element maxOccurs="0" minOccurs="0" ref="default_db__x3A__CRM_PROCES:PROCES_INIT"
                  id="_CRM_PROCES___d20e4581-1">
                  <xs:annotation>
                     <xs:appinfo>
                        <system_cache__appinfo:flat_relation_cache>
                           <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:CRM_PROCES_INIT/PARENT_ID"/>
                        </system_cache__appinfo:flat_relation_cache>
                     </xs:appinfo>
                     <xs:documentation>Tutaj nie dajemy appinfo relation cache - tylko w PARENT_ID do przetworzenia w celu odbudowania</xs:documentation>
                  </xs:annotation>
               </xs:element>
               <xs:element maxOccurs="0" minOccurs="0"
                  ref="default_db__x3A__CRM_PROCES:PROCES_GROUP_1" id="_CRM_PROCES___d20e4595-1">
                  <xs:annotation>
                     <xs:appinfo>
                        <system_cache__appinfo:flat_relation_cache>
                           <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:CRM_PROCES/PARENT_ID"/>
                        </system_cache__appinfo:flat_relation_cache>
                     </xs:appinfo>
                     <xs:documentation>Tutaj nie dajemy appinfo relation cache - tylko w PARENT_ID do przetworzenia w celu odbudowania</xs:documentation>
                  </xs:annotation>
               </xs:element>
               <xs:element maxOccurs="0" minOccurs="0"
                  ref="default_db__x3A__CRM_PROCES:PROCES_GROUP_2" id="_CRM_PROCES___d20e4602-1">
                  <xs:annotation>
                     <xs:appinfo>
                        <system_cache__appinfo:flat_relation_cache>
                           <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:PROCES_GROUP_2/PARENT_ID"/>
                        </system_cache__appinfo:flat_relation_cache>
                     </xs:appinfo>
                     <xs:documentation>Tutaj nie dajemy appinfo relation cache - tylko w PARENT_ID do przetworzenia w celu odbudowania</xs:documentation>
                  </xs:annotation>
               </xs:element>
               <xs:element maxOccurs="unbounded" minOccurs="0"
                  ref="default_db__x3A__CRM_PROCES:PROCES_BENEFIT_INFO"
                  id="_CRM_PROCES___d20e4609-1">
                  <xs:annotation>
                     <xs:appinfo>
                        <system_cache__appinfo:flat_relation_cache>
                           <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_PROCES:PROCES_BENEFIT_INFO/PARENT_ID"/>
                        </system_cache__appinfo:flat_relation_cache>
                     </xs:appinfo>
                     <xs:documentation>Tutaj nie dajemy appinfo relation cache - tylko w PARENT_ID do przetworzenia w celu odbudowania</xs:documentation>
                  </xs:annotation>
               </xs:element>
               <xs:element maxOccurs="unbounded" minOccurs="0"
                  ref="default_db__x3A__CRM_WSKAZNIK:CRM_WSKAZNIK" id="_CRM_PROCES___d20e4617-1">
                  <xs:annotation>
                     <xs:appinfo>
                        <system_cache__appinfo:flat_relation_cache>
                           <system_cache__appinfo:source system_cache__appinfo:name="ID" system_cache__appinfo:xpath="default_db__x3A__CRM_WSKAZNIK:CRM_WSKAZNIK/ID_PROCES"/>
                        </system_cache__appinfo:flat_relation_cache>
                     </xs:appinfo>
                  </xs:annotation>
               </xs:element>
            </xs:sequence>
         </xs:restriction>
      </xs:complexContent>
   </xs:complexType>
    and its default element to be aviable in API
    <xs:element name="PROCES_INIT" type="default_db__x3A__CRM_PROCES:PROCES_INIT"
      id="_CRM_PROCES___d20e4622-1_PROCES_INI"/>
  2. You can modell them by Derivation by extension of ComplexType the same way
Note: This is example of such file Example of Business Modelled Object CRM_PROCES.pdf

Business Objects Transformations Repository by Directory Structure Description

xmlschema-procesy5
public_html (Transformations Component)
config
config
Folder containing config for namespace binding feature. Needed by module object-engine to make correct API calls
NamespaceBinding.xml
This file contains database binding informations such like:
<system_cache__appinfo:NamespaceBinding xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://biuro.biall-net.pl/xmlschema_procesy5/default_db_xml_cache/appinfo.xsd ../default_db_xml_cache.public/appinfo.xsd"
 xmlns:system_cache__appinfo="http://biuro.biall-net.pl/xmlschema_procesy5/default_db_xml_cache/appinfo.xsd">
    <system_cache__appinfo:binding targetNamespace="https://biuro.biall-net.pl/wfs/default_db/SystemObjects/AccessOwner.xsd" bindPolicy="single">
        <system_cache__appinfo:prefix>default_objects</system_cache__appinfo:prefix>
        <system_cache__appinfo:api type="wfs">https://biuro.biall-net.pl/SE/version-git/wfs-data.php</system_cache__appinfo:api>
    </system_cache__appinfo:binding>
    <system_cache__appinfo:binding targetNamespace="https://biuro.biall-net.pl/wfs/default_db/SystemObjects/AccessGroup.xsd" bindPolicy="single">
        <system_cache__appinfo:prefix>default_objects</system_cache__appinfo:prefix>
        <system_cache__appinfo:api type="wfs">https://biuro.biall-net.pl/SE/version-git/wfs-data.php</system_cache__appinfo:api>
    </system_cache__appinfo:binding>
    <system_cache__appinfo:binding targetNamespace="https://biuro.biall-net.pl/wfs/default_db/SystemObjects/File.xsd" bindPolicy="single">
        <system_cache__appinfo:prefix>default_objects</system_cache__appinfo:prefix>
        <system_cache__appinfo:api type="wfs">https://biuro.biall-net.pl/SE/version-git/wfs-data.php</system_cache__appinfo:api>
    </system_cache__appinfo:binding>
    <!--<system_cache__appinfo:binding targetNamespace="https://biuro.biall-net.pl/wfs/default_db/SystemObjects/L_APPOITMENT_USER.xsd" bindPolicy="single">
        <system_cache__appinfo:prefix>default_objects</system_cache__appinfo:prefix>
        <system_cache__appinfo:api type="wfs">https://biuro.biall-net.pl/SE/version-git/wfs-data.php</system_cache__appinfo:api>
    </system_cache__appinfo:binding>-->
    <system_cache__appinfo:binding targetNamespace="https://biuro.biall-net.pl/wfs/default_db/SystemObjects/video.xsd" bindPolicy="singleStrip">
        <system_cache__appinfo:prefix>default_db</system_cache__appinfo:prefix><!-- in this example every primary id below @Strip is keept in <system_cache__appinfo:api> database ?proposal -->
        <system_cache__appinfo:api type="wfs" Strip="10000">https://video.biall-net.pl/SE/wfs-data.php</system_cache__appinfo:api>
        <system_cache__appinfo:api type="wfs" Strip="20000">https://video2.biall-net.pl/SE/wfs-data.php</system_cache__appinfo:api>
        <system_cache__appinfo:api type="wfs" Strip="30000">https://video3.biall-net.pl/SE/wfs-data.php</system_cache__appinfo:api>
    </system_cache__appinfo:binding>
    <system_cache__appinfo:binding targetNamespace="https://biuro.biall-net.pl/wfs/default_db/SystemObjects/images.xsd" bindPolicy="mirror">
        <system_cache__appinfo:prefix>default_db</system_cache__appinfo:prefix><!-- in this example every record is kept simulantuesly in several <system_cache__appinfo:api> database ?proposal -->
        <system_cache__appinfo:api type="wfs" >https://images.biall-net.pl/SE/wfs-data.php</system_cache__appinfo:api>
        <system_cache__appinfo:api type="wfs" >https://images2.biall-net.pl/SE/wfs-data.php</system_cache__appinfo:api>
    </system_cache__appinfo:binding>
</system_cache__appinfo:NamespaceBinding>
Note: This is experimental/in progress featureNamespaceBinding.xml
default_db_xml_cache (Transformations Component)
build_complexType.xsl (Transformations Component)
Generates xsd-style flat object
default_db.instance.xml (Directory) (Transformations Component)
build_complexType (Directory) (Transformations Component)
generated by build_complexType.xsl (Transformations Component) structurized flatten Business Data Object with the following informations:
  1. simpleType filters like:
    <xs:simpleType system_cache__appinfo:mode__build_flat_schema__match_simpleType_line="1408"
                           system_cache__appinfo:namespace_uri="http://www.w3.org/2001/XMLSchema"
                           name="int"
                           id="int">
               <xs:restriction base="xs:long"
                               system_cache__appinfo:namespace_uri="http://www.w3.org/2001/XMLSchema">
                  <xs:restriction base="xs:integer"
                                  system_cache__appinfo:namespace_uri="http://www.w3.org/2001/XMLSchema">
                     <xs:restriction base="xs:decimal"
                                     system_cache__appinfo:namespace_uri="http://www.w3.org/2001/XMLSchema">
                        <xs:restriction base="xs:anyAtomicType"
                                        system_cache__appinfo:namespace_uri="http://www.w3.org/2001/XMLSchema"/>
                     </xs:restriction>
                  </xs:restriction>
               </xs:restriction>
            </xs:simpleType>
    or like 
    <xs:simpleType system_cache__appinfo:mode__build_flat_schema__match_simpleType_line="1408"
                              system_cache__appinfo:namespace_uri="https://biuro.biall-net.pl/wfs/default_db/table/CRM_PROCES.xsd"
                              name="PROCES_INIT_Simple"
                              id="_CRM_PROCES___d20e4492-1_PROCES_INI">
                  <xs:restriction base="default_db__x3A__CRM_PROCES:TYPE_Simple"
                                  system_cache__appinfo:namespace_uri="https://biuro.biall-net.pl/wfs/default_db/table/CRM_PROCES.xsd">
                     <xs:restriction base="xs:string"
                                     system_cache__appinfo:namespace_uri="https://biuro.biall-net.pl/wfs/default_db/table/CRM_PROCES.xsd">
                        <xs:restriction base="xs:anyAtomicType"
                                        system_cache__appinfo:namespace_uri="http://www.w3.org/2001/XMLSchema"/>
                        <xs:enumeration value="PROCES_INIT"/>
                        <xs:enumeration value="PROCES_GROUP_1"/>
                        <xs:enumeration value="PROCES_GROUP_2"/>
                        <xs:enumeration value="PROCES_BENEFIT_INFO"/>
                        <xs:enumeration value="PROCES"/>
                        <xs:enumeration value="TEXT_BREAK"/>
                     </xs:restriction>
                     <xs:enumeration value="PROCES_INIT"/>
                  </xs:restriction>
               </xs:simpleType>
    Note: There You see full restriction with one set <xs:enumeration value="PROCES_INIT"/> to be used in this model.
p5_tr_map (Directory) (Transformations Component)
Transform Map in Name Space Prefix Directory (Transformations Component)
Directory contains after ex. /default_db/PROJECTS.xml files which are to be interpreted to bind to default Procesy5 storage database. And also another prefixes which could be bind to another database
Note: To be implemented another databases - IN PROGRESS
detect_resource_type (Transformations Component)
Object Dependency Analysis
Resource Relation Analysis in Name Space Prefix Directory (Transformations Component)
Described by resources_tree_generate_xsl_require_occurs_raport.xsd (Transformations Component) analysis containing at least the following:
  1. Encapsulated database prefix, master table and derived elementname="default_db__x3A__CRM_PROCES:PROCES_INIT
  2. system_cache__appinfo:detect_element_relations_to_objects_list
    1. system_cache__appinfo:detect_element_relations_to_objects
      1. system_cache__appinfo:ref="default_db__x3A__CRM_PROCES:PROCES_INIT"
      2. unique schema element @id system_cache__appinfo:id="_CRM_PROCES___d14e4407-1"
      3. type of data relation from p5_tr_map.xsd (Transformations Component) - system_cache__appinfo:event_type="477"
      4. if relation needs some derivation instructions to be used to instantiate object - p5_tr_map:relation_after_derivation="true"
  3. p5_tr_map:objects_derivations_list
    1. dereviation_count="2", p5_tr_map:parent_name_with_pref="default_db__x3A__CRM_PROCES:CRM_PROCES", p5_tr_map:parent_id="_CRM_PROCES___d14e4403-1_CRM_PROCES", p5_tr_map:object_type_name_with_pref="default_db__x3A__CRM_PROCES:PROCES_INIT", p5_tr_map:object_type_id="_CRM_PROCES___d14e4414-1_PROCES_INI"
      1. One or more definitions in element p5_tr_map:derivations
        1. local-name="complexType"
        2. system_cache__appinfo:name="PROCES_INIT"
        3. system_cache__appinfo:id="_CRM_PROCES___d14e4414-1_PROCES_INI"
        4. system_cache__appinfo:prefix="default_db__x3A__CRM_PROCES"
        5. p5_tr_map:name_with_pref="default_db__x3A__CRM_PROCES:PROCES_INIT"
        6. system_cache__appinfo:xpath_full="default_db__x3A__CRM_PROCES:PROCES_INIT"
  4. system_cache__resources_tree_generate_xsl_required_occurs_raport:parent_complexType_siblings_list/system_cache__resources_tree_generate_xsl_required_occurs_raport:parent_complexType_siblings
    1. system_cache__appinfo:parent_complexType - system_cache__appinfo:name="CRM_PROCES", p5_tr_map:name_with_pref="default_db__x3A__CRM_PROCES:CRM_PROCES" - where is real resource, system_cache__appinfo:id="_CRM_PROCES___d14e4403-1_CRM_PROCES", , local-name="complexType"
      1. system_cache__appinfo:parent_complexType_child
        <system_cache__appinfo:parent_complexType_child system_cache__appinfo:name="CRM_PROCES"
                                                               p5_tr_map:name_with_pref="default_db__x3A__CRM_PROCES:CRM_PROCES"
                                                               system_cache__appinfo:id="_CRM_PROCES___d14e4403-1_CRM_PROCES"
                                                               system_cache__appinfo:prefix="default_db__x3A__CRM_PROCES"
                                                               local-name="complexType"
                                                               system_cache__resources_tree_generate_xsl_required_occurs_raport:derived_appropriate="true"/>
               <system_cache__appinfo:parent_complexType_child system_cache__appinfo:name="CRM_PROCES"
                                                               p5_tr_map:name_with_pref="default_db__x3A__CRM_PROCES:CRM_PROCES"
                                                               system_cache__appinfo:id="_CRM_PROCES___d14e4413-1_CRM_PROCES"
                                                               system_cache__appinfo:prefix="default_db__x3A__CRM_PROCES"
                                                               local-name="element"
                                                               system_cache__resources_tree_generate_xsl_required_occurs_raport:derived_appropriate="true"/>
               <system_cache__appinfo:parent_complexType_child system_cache__appinfo:name="PROCES_INIT"
                                                               p5_tr_map:name_with_pref="default_db__x3A__CRM_PROCES:PROCES_INIT"
                                                               system_cache__appinfo:id="_CRM_PROCES___d14e4414-1_PROCES_INI"
                                                               system_cache__appinfo:prefix="default_db__x3A__CRM_PROCES"
                                                               local-name="complexType"
                                                               system_cache__resources_tree_generate_xsl_required_occurs_raport:derived_appropriate="true"/>
               <system_cache__appinfo:parent_complexType_child system_cache__appinfo:name="PROCES_INIT"
                                                               p5_tr_map:name_with_pref="default_db__x3A__CRM_PROCES:PROCES_INIT"
                                                               system_cache__appinfo:id="_CRM_PROCES___d14e4426-1_PROCES_INI"
                                                               system_cache__appinfo:prefix="default_db__x3A__CRM_PROCES"
                                                               local-name="element"
                                                               system_cache__resources_tree_generate_xsl_required_occurs_raport:derived_appropriate="true"/>
(…)
  5. informations about relations to another objects system_cache__appinfo:objects_parent_relation
  6. informations about other objects relations to this one analyzed system_cache__resources_tree_generate_xsl_required_occurs_raport:from_parent_relations_list
table (Directory) (Transformations Component)
table (Directory) (Transformations Component)
This is the main repository of Customized Business Objects in XML Schema to be analyzed by Business Objects Transformations Component like build_complexType.xsl (Transformations Component), p5_tr_map.xsl (Transformations Component) or build_complexType.xsl (Transformations Component).
  1. This objects are intend to be instantiated in default_db prefix Procesy5 Process (BPMN) Database. It contains the Business Objects Transformations Namespaces, Prefixes handling and modelling style models.

Procesy5 Resources Controll

Integrated Procesy5 Schooling system

Integrated Procesy5 Schooling Capabilities

Short descriptions of tasks / process
They conforms to BPMN Task
Long descriptions with pictures
It is capable to write many text with also pictures
Schooling material order (sorting)
Schooling material can be sorted from most important to less important or to fix correct order of learning
Testing and Certification
Open Question
It should be verified by person with access to the module to test if such answers were correct and give them note
Test Verifier Module
Person Certificate
System provide automatic certificate generation with actual person tests results
Person Knowledge Overwiev
Current Knowledge
We can see what processes person should have read, what is the result
Not actual Knowledge
We can see what process have changed and the person didnt verified that

Rapid implementable Print templates framework glossary

Simple Template document with data relation info

For rapid printing pdf templates development consider use for standard we use standarized format for templates which easily can be associated to our System API . By using our templates You can easily create PDF files from default api. This is the example of template to print user associated physical resources, without reccurence:
<?xml version="1.0" encoding="UTF-8"?>
<RelatedFeature xpath="ID"  typeName="p5_default_db:ADMIN_USERS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
  xsi:noNamespaceSchemaLocation="../../../default_db_xml_cache.public/topicProcesy5.xsd">
<topic id="untitled4" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:noNamespaceSchemaLocation="urn:oasis:names:tc:dita:xsd:topic.xsd">
  <title><ph>Dane wyposazenia dla </ph><ph xpath="ID"/><ph>-</ph><ph xpath="ADM_NAME"/>
    </title>
  <body>    
    <p><b>Wyposażenia</b></p>
    <p>
      <table>
        <tgroup cols="4">
          <thead>
            <row>
              <entry>ID</entry>
              <entry>TYP</entry>
              <entry>s/n</entry>
              <entry>koszt</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry/>
              <entry/>
              <entry/>
              <entry/>
            </row>
            <RelatedFeature xpath="ADMIN_USERS_ID" xpath_value="../ID" typeName="p5_default_db:DEVICES">  <!-- test sciagniecia powiazanych pism do sprawy -->
                <RelatedFilter xpath="PARENT_ID" xpath_value=""/>
              <!-- to disable copied records  -->
              <row>
                <entry xpath="ID" />
                <entry xpath="T_DEVICE_TYPE"/>
                <entry xpath="T_DEVICE_SERIAL"/>
                <entry xpath="F_BILL_COST"/>
              </row>
              <RelatedFeature xpath="PARENT_ID" xpath_value="../ID" typeName="p5_default_db:DEVICES">  <!-- test sciagniecia powiazanych pism do sprawy -->
                <row>
                  <entry xpath="ID" >Parent</entry>
                  <entry xpath="T_DEVICE_TYPE"/>
                  <entry xpath="T_DEVICE_SERIAL"/>
                  <entry xpath="F_BILL_COST"/>
                </row>
              </RelatedFeature>
            </RelatedFeature>
          </tbody>
        </tgroup>
      </table>
    </p> 
  </body>
  </topic>
</RelatedFeature>
the sample output is Sample template ouptut .pdf
Note: that we used there relations from fields and not system ref and instances in this example (for ease of task description)

Data Relation Handling subsystem

Search by Relations

Note: To be specified and in development

Data Instances Handling subsystem

Data Instances Handling subsystem

Every Business Data Object has its root ComplexType which is then applied Modelling Business Objects with Derivation by extension of ComplexType or Derivation by restriction of ComplexType.

In Procesy5 interfaces GUI Development user is allowed to run Process modified by Modelling Business Process, stored in Procesy5 Process (BPMN) Database. This processes has Association By Business Object, and depending on that User can insantiate certain type of allowed Instance.

According to that there are possibility to match certain instances and make and different possibility of Data Relation Handling subsystem.

Different type of instances are aviable in System API by different TYPENAME.

Primary Key handling

Primary Key Handling in Data Business Objecs binded to Local Storage
use key Primary xs:unique definitions

Timestamp handling

System provide data for Timestamp informations to make aviable requests by modification date
Note: To be defined in api method

Modification History handling

System provides full history table which is used to Rollback Data

Rollback Data

Rollback Last Edit
Is aviable in WEB gui for especially geometry data
Rollback by User and Date
Note: In development

Lock Instance for Edit

Note: currently in development

Data Business Objects Modules

Ant Data Business Object Module

Business Object Template Triggers

Local and Foreign Template Triggers
Template Trigger Before Insert to Local Object
Template should modify input data to provide summarized field in current single object only
Template Trigger After Insert

Procesy5 Automation Development

Automation Controllers

Procesy5SerialController NMEA/RS485

P5AutomationSerialController Device is the first native communicated hardware device which allows to controll of external automation devices with the main task of prompt monitoring standarized automation outputs in RS485 or NMEA2000 standard

External / standards terms

XML standard elements

Element

Attribute

Namespace

Xlink Reference

XML-Schema

XML-Schema

The most modern and advanced standarization of formal notation targeted on data structure specifications. System API is capable of understanding this notations. This technology is capable for developing and documenting Business Objects

TargetNamespace

It should be unique for exact type of object. This is example Namespace declaration attribute in <xsd:schema> root element xmlns:default_db="http://biuro.biall-net.pl/xmlschema_procesy5/default_db".

In System API they are used to bind them to correct Procesy5 storage database and its tables

SimpleType

It definies data type for Element for example or it can contains string or int or another types

Sequence

Choice

All

key

key Primary xs:unique
  1. Allow to set primary key which is than used as FeatureID in API requests

Instances

Instance

Incorrect Instance

expected reference not occurs
expected reference occurs too much
expected element not found
not expected element

Modelling Business Objects

Modelling Business Objects Methods

Derivation by extension of ComplexType
This adds some extra some new Element to ComplexType
Adding child Elements simpleType
  1. Elements can have standard type like xs:int , xs:date or xs:string and many others conforming to XML-Schema standard.
  2. Elements can be set type for Customized simpleType, limiting standard XML-Schema
Adding reference to Root Elements
Defining Foreign Dictionary Relation Schema Specification

When You want to enable relations handling in Namespace Binding Data Business Object to Remote Foreign Storage by using expected known elements/fields, You should make the following specifications:

<xs:element ref="default_db__x3A__COMPANIES:ID_BILLING_USERS"
            id="default_db__x3A__IN7_DZIENNIK_KORESP___d13e9926-1">
            <xs:annotation>
               <xs:appinfo>
                  <system_cache__appinfo:flat_relation_cache>
                     <system_cache__appinfo:source system_cache__appinfo:name="ID_BILLING_USERS" system_cache__appinfo:xpath="default_db__x3A__COMPANIES:ID_BILLING_USERS/ID"/>
                  </system_cache__appinfo:flat_relation_cache>
               </xs:appinfo>
            </xs:annotation>
         </xs:element>
system_cache__appinfo:flat_relation_cache contains system_cache__appinfo:source with following attributes:
  1. system_cache__appinfo:name="ID_BILLING_USERS" - means that local field is ID_BILLING_USERS
  2. system_cache__appinfo:xpath="default_db__x3A__COMPANIES:ID_BILLING_USERS/ID" - means that we expect in foreign object that element ID be the same as ID_BILLING_USERS in local object
Customized simpleType
simpleType can set certain type of data by restriction of maxlength etc, conforming to XML-Schema

Modelling Business Process

BPMN flow elements

BPMN Event
BPMN Task
BPMN Gateway

BPMN resources association elements

BPMN lane
To directly associate some BPMN flow elements that they are subject to be executed by one of

Business Objects Definitions

Business Object Human Resource

This type of object is standard Resource that is subject to evidence in Procesy5 Resources Database. It fits the following needs:
  1. Should be able to be associated to some of the Procesy5 Process (BPMN) Database by the Procesy5 ProcessEditor
  2. Should be able to add/modify/edit by the Procesy5 ResourcesModeller and keep in Procesy5 Resources Database
By supporting the advantages of our Modelling Business Object methods it should be also able to work the same way like Business Physical Resource Object.

Business Physical Resource Object

This object class is intend to represent some real physical structure of object, which is intend to be controlled and managed. By controlling such objects it is usually so be planned and organized by the following tasks:
  1. Modelling Business Object with also making Xlink Reference or from other side Derivation by extension of ComplexType to some existient Business Objects
  2. By discovering and Modelling Business Objects you the same time plan the Instance where this structure will be stored in Procesy5 storage database with also setting Namespace binding method.
    Note: This is status WORK IN PROGRESS
  3. Object can be controlled by Physical Business Resources Controll

Automation terms

RS485

Standarized method and port for communication automation by using wired transmission

CAN

Standarized RS485 by vehicle manufacturers. It allows powering nodes and also some concurent priority transmissions

NMEA 2000

It is more standarized CAN The standard in communication between devices common used in marine and yachting

i2c or another technology to internal multi-chip communications

PROFIBUS

Communication standard for querying /communication with automation modules and controllers