Start with a page the records can support
Views are supported in Mensara 0.20.11 with Portal 0.3.47 or later. Check your installed version before starting. A compatible connected agent can build a View with the Mind tools; it does not need a local coding shell.
Tell your agent what the page should show, which saved records it should use and the people who will open it. For example, a fictional pipeline board might show stage, owner and next step from deal records. Ask it to inspect the actual records before promising fields or counts.
Put private information in a private area
A View reads as its viewer, within its declared areas and the authors’ current access. It cannot grant access to a record. If private fees and ordinary deal information need different audiences, keep them in separately protected areas. Removing a column from the design does not protect a field stored in a file the viewer can read.
The author needs permission to propose the View’s bundle in the operations area and to read the records it should show. If the author cannot read an area, their View cannot show it to other people either. Choosing access explains the underlying permissions.
Describe and check the draft
Ask the agent to use the view-builder skill. Agree the page’s address and the records it will use. Before proposing files, have it describe the layout and expected empty or incomplete states in ordinary words. The View is read-only: it cannot write records, run on a schedule or fetch information from the internet.
The agent validates the complete bundle with a dry run. That checks the bundle contract, not whether its datasets contain the correct records. Inspect the proposed page and the real data separately. The build procedure gives the agent’s exact validation and lifecycle calls.
Have another person approve and publish
The author cannot approve their own View. Another authorised owner or admin reviews the complete proposed files, approves the bundle and separately publishes it. A held proposal is still waiting. Approval alone is not a published address.
After publication, open the address as the intended viewer. Compare a few rows with their saved sources. Check the empty and partial states and a harmless excluded record. Opening a team View explains why different people can see different rows.
Build, review, publish and check
A valid draft and a published page are separate results.
The author builds a complete View bundle and validates its contract. A different authorised person reviews and approves the exact files. Publishing installs that approved release at its route. Open the route as an intended viewer and compare its rows with saved sources; data remains limited by the viewer’s access and every author’s current access.
Change or remove the page
For an update, have the agent read the current bundle, raise its version, validate and propose the complete replacement. Another authorised person approves it, then upgrades the installed View. Do not edit installed files and assume they are published.
The supported lifecycle also allows rollback to the previous approved version, suspension to hide the View and removal to free its address. Inspect the resulting state and address after each action. These actions change the page’s availability; they do not delete the underlying business records.
Related
Practical guides for people and agents