How can we help you?

Advanced documentation search

Permissions, Actions, and Error Codes Reference

Product: FeraRender Topic: Reference Versions: Applies to all documented versions Current
Written by user
Updated

Find permission names, audit actions, log categories, and stable error identifiers.

Audience: Administrators, developers, and support staff
Recommended visibility: Public

Overview

Find permission names, audit actions, log categories, and stable error identifiers. Use this article as a field and behavior reference. Verify release-specific values against the current service before publishing exact versions or product limits.

Key points

  • Permissions include VIEW.TEMPLATE, EDIT.TEMPLATE, CAN.RENDER, and the configurable native-XSLT permission.
  • Actions include template viewed, template edited, dataset updated, mapping updated, and render.
  • Important error identifiers include mapping required, compilation required, declaration conflict, invalid fragment, invalid composite, and invalid dataset.

Recommended procedure

  1. Locate the relevant object, status, permission, or code.
  2. Confirm tenant and version context.
  3. Apply the documented rule consistently.
  4. Escalate conflicts between this reference and current API behavior for documentation review.

Troubleshooting

The documented value differs from a response

Record the service version and route, then update the draft or implementation before publication.

A field appears unused

Check legacy routes, UI clients, imports, and migration code before removing it.

A status persists unexpectedly

Inspect validationJson, compiled resources, assignments, and recent source changes.

Related documentation

Documentation source: feradelinc/feradel.render.api, reviewed against repository revision b2c3a710. Verify behavior against the deployed release before publishing exact routes, limits, or version requirements.