Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The feature is specific functionality users can use in an application. In other words, an application is made up of on the application that can be used by users of the subscriber instance. An application can have multiple features. Features can be of two types standard and customwill be accessible by the user of the subscriber instance as per the assigned license. There are is categories of features: Standard and Custom.

Standard

...

feature

standard Standard features are defined by PWR Apps and hence available throughout the orgavailable to all instances.

Custom

...

feature

custom Custom features are those defined by you publishers while creating an application, as . As they are custom they features, the name of the feature will be differentiated on prefixed with the basis of instance prefixID.The feature can be of the following data types:

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 scope of the feature is instance and the checkbox value is true then we will get to know all the users of that instance have access to that particular feature and if the checkbox value is false then we will get to know if any instance or user has no access to that particular feature. checkbox type of feature would be a custom type of feature. The checkbox type of feature has no reset period and the scope of the checkbox feature could be an instance or user. This indicates whether the users have access to this feature or not with the values TRUE or FALSE.

Records:

Records indicate the number of records can a user can create using that feature, a record would be a custom type of feature. records type of feature has no reset period and the scope of the feature could be an instance or user.

  • Numbers:

The number on a license object

Numbers:

This type of feature indicates how many times the user can use this feature. For example, the user to which this feature's license is assigned can consume a number of documents printed per day, after that the user will get an error that “Allocated amount is exhausted”.

API:

This type of feature indicates the number of records can user create using that feature. we can reset the number type of feature annually or daily. scope of the number type of feature could be user or instance i.e if the scope is user then the feature assigned to a user can have access to that feature and if the scope is instance then all the users have access to that instance have access to that feature.

  • API:

API type of feature indicates a number of APIs that can use in that feature. we can reset such feature monthly and the scope of API type of feature would be an instance

  • Storage:

The storage type of feature has no reset period and scope of such feature would be instance onlyAPIs users can consume. For example, all users together in the instance can consume max n numbers of a particular API per year, after that, they will get an error that “Allocated calls are exhausted”.

Storage:

The total number of records can be created in the given instance. Scope for storage feature type will be instance only. The storage type feature will not have a reset period property

Scope

Instance:

If the scope of the feature is an Instance. It means this particular feature is available for all the users of the instance.

User:

Features with this scope will be user-based, this will be only available for the users to which this feature's license is assigned.

Reset Period

Daily:

The used amount will reset to zero every day at 00:00 AM as per the instance timezone.

Monthly:

The used amount will reset to zero on the 1st day of every month at 00:00 AM as per the instance timezone.

Annual:

The used amount will reset to zero on 1st Jan at 00:00 AM of instance timezone.

Never:

The used amount will never reset