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 on the application that can be used by users of the subscriber instance. An application can have multiple features. Features will be accessible by the user of the subscriber instance as per the assigned license. There are is categories of features: standard Standard and customCustom.
Standard feature
Standard features are defined by PWR Apps and hence available throughout the orgavailable to all instances.
Custom feature
Custom features are those defined by you publishers while creating an application, as . As they are custom feature names features, the name of the feature will be prefixed with the 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 . This indicates whether the 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 featurethis feature or not with the values TRUE or FALSE.
Records:
Records indicate the number of records can a user can create on an object using that feature.a license object
Numbers:
The number This type of feature indicates the number of APIs can a user use using that how many times the user can use this feature. For example, the user to which this feature's license is assigned can consume n APIs a number of documents printed per day, after that he the user will get an error that his allocated “Allocated amount is exhaustedexhausted”.
API:
API This type of feature indicates a the number of APIs users can have access toconsume. 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 “Allocated calls are exhaustedexhausted”.
Storage:
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.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 that means it will indicate all users together in the instance can use that featureInstance. It means this particular feature is available for all the users of the instance.
User:
If the scope of the feature is user then that means a Features with this scope will be user-based feature so only , this will be only available for the users to which this feature's license is assigned can use that feature in the app..
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