Related links
Framework Core functionality
- AyMINE Framework Server
- Configuration of the user-defined fields
- Framework dependency on the open-source libraries
- Client-Defined attributes
- Default server methods
- User sessions
- Import collection of objects
- Multi tenant Architecture
- The AyMINE licence model
- Export collection of objects
- Strings and translations
- System messaging
- System Rights
- File Management with End-to-End Encryption
- Server configuration for large files
SOA Architecture
Support for Service Object Architecture and Internal Event ManagementLibraries & Lincences
Module - support for management
Front-End Scripting
System Management
- SaaS Management Module
- Management of the SaaS service client
- Encryted wallet storing access keys for data vault
- Definition and Management users in the SaaS system
- Management of the system users
- System right management
- System role is how user administrator sets the rights
- File access, storing and locking
- Communication geateways
- Private Object Marks, Sign & Notes
Task Management Module
- About TSK module
- Support for voting and decision management
- Support and implementation notes for FMEA
- Support for the Methodology Management
- Project Methodology Support
- Project Roles - Data model and implementation notes
- Actions and Meeting Agenda
- Description of person and supplier competencies
- Business event
- Problem & Helpdesk management support
- TSK module releases
- User Reminder
Task & Task pattern
Mobile & Web Application
- clientprogramming_fevaldataobject
- userinterface-objectstructure
- cliplink
- npmlibraries
- fclip
- drag-drop
- AyMINE Application
- objectdefinition_inlineedit
- npmlibraries_stringlibrary
- clientprogramming
- mobileapplication
- languagesupport
- objectdefinition_multiupdate
- Object API – object <g>
- clientprogramming_fevallanguage
- clientprogramming_fevaluser
- objectdefinition_viewdefinition
- offlineobjects
- System console
- Runtime debugging
- objectdefinition_detailview
CMS - Content Management & Web API services
FI - Finance Management
Sales & Asset management
Sales related services
Description of a part of the AM module - sales partHR - Human Resources
New object at created at the server
Guidelines how to create new object at the server and open the detail view with new object.
When pattern used
Pattern is used, when user creates object:
- Object is linked in complex structured that should be set directly before user can edit object
- When more than single object is created at once
- When object should have pre-set attributes that cannot be set by default from jsonc
Pattern
Pattern is defined in the script orchestration
Step 1: Request object by client:
User starts operation that request new object. Operation is used instead common insert
"server.tskEvent.createNewRaised(tskAreaID=@oAttr.tskAreaID)",
Step 2: Server creates object
Server creates object and returns it's id in return attributes:
$resp = Response::OK();
$resp->addRetVal('newID', <$newObjectID>);
return $resp;
Step 3: Client opens object
Client opens detail and passes the return field to the oID attribute of the detail
"form.<objectName>.detail.(oID=@fAttr.newID,location=modal)",
Notes:
- Name of the returned field (newID in this case) is not predefined; @fAttr should be used to pass the attribute, not the object field oID.
- Field oID – when defined as a attribute – is automatically set to be from the viewDef attribute group, so that explict definition
oID:viewDef=is not necessary.
Complete example
Complete orchestration method is from tskEventObjectRel:
"newRaised":{ "icon":"new", "multi":0,
"command":[
"server.tskEvent.createNewRaised(tskAreaID=@oAttr.tskAreaID)",
"form.tskEventObjectRel.detail.raisedEvent(oID=@fAttr.newID,location=modal)",
"window.reload"
]
}