Thinking in neome

Create reusable parts

• A form is used for data exchange or storage.
• A form contains a set of sections and grids.
• A section includes a set of fields to allow one-to-one relationships.
• A grid has a set of rows, each containing a set of fields to enable one-to-many relationships.
• The variable allows a value to be reused across the backend, frontend, and forms.
• Forms and variables are reused across the app and created when required.

Create spreadsheets

• App's data is stored in spreadsheets.
• To specify the kind of spreadsheet data associate a form.
• There are special fields called Ref fields that allow one spreadsheet to refer to another. For example, FormOrder of OrderSheet can refer to FormItem from ItemMaster.
• To make the spreadsheets queryable and searchable, you provide a set of fields on which the platform will create appropriate indexes for faster querying and searching.

Create reports

• Create reports to extract data out of spreadsheets.
• A report takes an input form argument to provide an output form. For example, ReportGetOrders could have InputDateRange as the input form and OutputOrderList as the output form.
• Unlike traditional reporting engines, neome does not provide a cursor of records. You only get one output form.
• For simple reports, neome has visual query builders; for complex reports with multiple spreadsheet joins, neome provides neoQL query language.

Create layouts

• With layouts attached to the form and spreadsheet, control what end-users will see.
• Can associate multiple layouts with forms and spreadsheets and switch between them.

Import plugins

• Use plugins to integrate with a set of external systems.
• Plugins are downloaded and executed by neome agent within your data center.
• Reuse plugins from a library or create custom plugins.

Automate

• Automate manual tasks with built-in automation kit.
• Do not worry about automation initially; first, get the manual workflows right by building both the backend and frontend, then add automation to optimize manual steps.
• Automation is not an alternative to plugins or code.

Roles and permissions

• Almost everything in neome has role-based access and permissions. An enterprise app can control who can see and do what at the most granular level.

Create actions

• Actions expose the underlying backend function like spreadsheet row insert, spreadsheet editor, report, or audit trail.
• Action ties label, icon, tooltip, and default input forms for the underlying backend function.

Create groups

• Groups provide role-based access to actions.
• Groups also determine if specified roles can chat.

Create deeplinks

• Deeplinks, like actions, expose underlying backend functions that can be sent as hyperlinks in emails, SMS, WhatsApp, etc.
• Can control visibility, expiry, and WhatsApp preview of the deeplink.
• Can use deeplinks to embed appropriate user interface in external apps with zero coding.

Create drive

• Specific spreadsheets can be downloaded on your laptop through drive sheet configuration.
• Can control spreadsheet data partitions, update duration, retention, priority, and media downloads.

Create prompts

• While deeplinks are outbound, prompts are inbound. Associate a prompt with action invocation.
• With prompts and deeplinks entire workflows can be started and finished through email, SMS, or WhatsApp.

Create translations

• Provide translations to almost every text element to allow multi-lingual support in the application.