Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 16 Next »

The feature is specific functionality users can use in an application. In other words, an application is made up of multiple features. There are two categories of features: standard and custom.

Standard feature

Standard features are defined by PWR Apps and hence available throughout the org.

Custom feature

Custom features are those defined by you while creating an application, as they are custom feature names of the feature will be prefixed with instance ID.

Feature type

Checkbox:

A checkbox is a boolean type of feature type it will store value in a boolean format i.e true or false. That means if the checkbox value is true then we will get to know users have access to that particular feature and if the checkbox value is false then we will get to know the user has no access to that particular feature.

Records:

Records indicate the number of records can a user create on an object using that feature.

Numbers:

The number type of feature indicates the number of APIs can a user use using that feature. For example, the user to which this feature's license is assigned can consume n APIs per day, after that he will get an error that his allocated amount is exhausted.

API:

API type of feature indicates a number of APIs users can have access to. For example, all users together in the instance can consume max n API per year, after that, they will get an error that allocated calls are exhausted.

Storage:

Standard, system and metadata records creation can be controlled using feature type storage. scope for storage feature type will be instance only. The storage type feature will not have a reset period property

Reset Period

Never:

There may be some features that will not need reset for example orektic__timesheet feature does not need any reset.

Daily:

There will be some features that will get reset daily i.e after every 24 hr. For example, API usage has to be reset on the basis of the day (24 hr).

Annual:

There will be some features that will get reset annually, for example, there are some APIs whose usage has to be reset annually.

Monthly:

There will be some features that will get reset monthly, for example, orektic_timesheetAPI feature needs a monthly reset property.

Scope

Instance:

If the scope of the feature is an instance that means it will indicate all users together in the instance can use that feature.

User:

If the scope of the feature is user then that means a user-based feature so only users to which this feature's license is assigned can use that feature in the app.

  • No labels