Related links
Sales & Asset management
Sales related services
Description of a part of the AM module - sales partFI - Finance Management
Framework Core functionality
- AyMINE Framework Server
- frmFrm – provided functionality
- System Rights
- System messaging
- AyMINE Business – Price calculation
- Strings and translations
- Export collection of objects
- AyMINE Framework management FAQ
- The AyMINE licence model
- AyMINE On-premise
- System events
- Mutli-client architecture
- Import collection of objects
- User sessions
- Default server methods
- Client-defined object attributes
- Common Libraries
Module - support for management
Libraries & Lincences
Mobile & Web Application
- Runtime debugging
- System console
- AyMINE Application
- In-line table edit support
- Object scripting API – object lang
- Application object structure
- Multilingual support
- View of a single object – detail
- Is using EVAL / feval method risky?
- Included library – String operations
- Cliplink
- Object API – object <g>
- API – Data object
- Object scripting API – object User
- Object view definition
- Framework support for Drag & Drop
- Common libraries
- Multiple-object update implementation
- fClip & fCliplist
- Offline persistent objects
- Mobile application
HR - Human Resources
System Management (part of framework)
Task, Project, Quality
Task & Task pattern
CMS - Content Management & Web API services
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"
]
}