CompuTec WebUp

Mark fields as mandatory to ensure critical data is captured before a document is saved, or set fields as read-only to protect key data from being changed.

Control how a field presents its data: set the input type (for example, display a numeric field as a quantity), limit the maximum length, and adjust text alignment and direction.

Give a field a warning, error, or information value state with a colored background and a message shown on focus, guiding users toward correct input at the point of entry.

Link control values to live SAP Business One data model fields, for example, displaying a calculated total or a related document value directly on screen.

Use SAPUI5 expression binding to drive control properties from live data, so a field becomes visible, mandatory, read-only, or highlighted only when another field meets a defined condition.

Actions run before or after document events (On Add, On Update, On Cancel, or On Close), giving precise control over when automation logic executes.

Build automations that respond to document events, such as creating a follow-up Activity or updating a field value when a Sales Order is updated. Automations can post new SAP Business One documents through the Service Layer, not only change the current screen.

Write and edit JavaScript using the same high-performance code editor that powers Microsoft Visual Studio Code, with IntelliSense for smart code completion and SAP Business One data model validation built in.

Speed up script development using built-in templates for common tasks and reusable code snippets for single-line operations, formatting, and conditional checks.

Test any automation in real time within the SAP Business One Web Client before activating it, using the built-in preview mode.

Validation rules can run before or after a user adds, updates, cancels, or closes a document, giving control over exactly when data is checked.

Build validation rules based on conditional logic, for example, if one field contains a specific value, require or restrict another field accordingly.

Display clear, custom messages when validation conditions are met, alerting users to missing or incorrect data or asking for confirmation before proceeding.

Validation messages can provide specific guidance on what needs to be corrected, helping users resolve issues without needing to contact support.

Write validation scripts using the Monaco Editor with IntelliSense and SAP Business One data model validation, keeping validation logic accurate and easy to maintain.

Unlike View Actions which respond to document events, Smart Actions attach directly to individual controls. They are triggered when a user edits a field, presses a button, or interacts with any UI element.

Define a Smart Action once and reuse it across multiple screens and views at Global, Object, or Local scope depending on where the logic needs to apply.

Smart Actions support parameters that pull live values from the SAP Business One data model, so confirmations, validations, and actions always reference current document data.

A single Smart Action can retrieve and display information such as a business partner snapshot, validate input as a user works in a field, update master data, or post a new SAP Business One document through the Service Layer.

Display dynamic confirmation messages at the exact moment of user interaction, for example, asking a user to confirm before changing a price field or saving a critical document.

A built-in Help Mode places question-mark icons throughout the configuration interface, each linking straight to the relevant SAP Business One Web Client extensibility documentation, so help is always one click away.

Maintain several named views for the same screen, each holding its own layout, controls, actions, and validations. One view and version is active per screen at a time.

Every change to a view creates a new version automatically, while the previous version remains active as a backup so you can roll back at any time without losing data.

Changes remain in draft until you are ready to activate them, allowing configurations to be tested and validated before going live via the built-in preview mode.

All inactive versions are archived with timestamps, supporting audit trails, diagnostics, and compliance requirements.

All configurations are saved directly in your company database, keeping customization data inside your SAP Business One environment.

Configurations that follow the SAP Business One Web Client Extensibility Framework are deployed as standard SAP Web Client Extensions, reducing the risk of conflicts when SAP Business One is updated.