Z-Studio
The admin office needs a page to look up suppliers, with a button to file a purchase request. IT builds it in Z-Studio, reads the list from Z Data and wires the button to an approval process. Once published, the app shows up in the menu of the people allowed to open it.
An app is one or a few pages. Each page holds data tables, short instructions and buttons. Tables read only from datasets published in Z Data, and the system checks on save that the dataset exists.
A button either starts a process or refreshes the data. To file a request or update a record, the user presses a button that runs an approval process designed in Process. The app never writes to the data store by itself, so each change has an approver and a trail.
When publishing, the admin picks the roles or people allowed to open the app. It appears in their menu and nobody else sees it. Users always run the published version, and drafts can only be previewed by the designer.
Every save creates a new version, and the running app is untouched until you publish again. Saves and publishes are written to the audit trail, so you know who changed the app and when.
People using an app need nothing extra. Building an app currently means editing a structured page definition, so it suits IT staff or people used to configuration. A visual drag-and-drop designer is not in this release.
Z Data holds tables and datasets. Z-Studio builds the screens where people view that data and press buttons that start processes. The two are usually used together.
No. Apps, versions and access grants are kept separate per organisation. What an app shows comes through that organisation's own Z Data and processes.
Leave your details and we will call you within one working day to set a time. The demo takes about 30 minutes and focuses on the departments you care about.
Or email us: [email protected]
