Features

The following are the key features available in Enterprise Store (ES) 2.1.0:

Feature	Description
Asset type extension mechanism	Add new asset types to ES (e.g., APIs, Web apps, mobile apps and services) that can be accessed all in one store.
Asset extension mechanism	Customize views of each asset type based on required preferences in the Store and the Publisher.
App extension mechanism	Customize cross-cutting changes in the Store and Publisher, which affects all the asset types globally.
Role-Based Access-Control (RBAC) for asset types	The permission model in WSO2 ES provides: Control as to what role each asset is visible in each state (e.g., only a user with the reviewer role can promote an asset from the In-Review state to Published in the gadget lifecycle). Control access to pages, APIs and UI elements of pages.
Asset lifecycle customization	Customize the asset lifecycle based on the asset type.
Subscription process customization	Customize the subscription process relevant to the particular asset type (such as, download an eBook, subscribe to an API and install a mobile app).
REST API interface	REST API interface available to manage assets and access lifecycle information.
Asset Lifecycle Transition Notifications	Email notifications for asset lifecycle transitions, which are configurable for user roles.
Password recovery	Enable password recovery, so that WSO2 ES users who have forgotten their password can reset their password.
Pre-loaded provisioning for default assets	WSO2 ES comes pre-loaded with provision for gadgets, websites with extensions available for apps and REST and SOAP services.
A variety of search options	The Store and Publisher has the following search options. Search history - Ability to reuse search queries without having to retype the query. Search by adding keywords - Ability to add one or more keywords in the search query. Search using the advanced search - Ability to search based on asset attributes, tags and/or categories. The asset attributes vary based on the asset type. This search option is only available in the Publisher. For more information, see Searching for an Asset in the Publisher and Searching for an Asset in the Store.
Search history capabilities	WSO2 ES is capable of tracking the user search history in the Publisher and Store. When assets are searched for in the Publisher or Store, those search queries are automatically stored. Therefore, users do not lose their search history results even when the session is destroyed. Furthermore, WSO2 ES maintains the search history based on the asset type (e.g., the search history for gadgets and the search history for sites are different). Therefore, separate search histories for each asset type are available in WSO2 ES.
Asset sorting via the Store	Sorting of assets based on the popularity, name and/or date created.
Store social platform	Social interaction among users in the Store with the option of adding an asset review, rating, and liking or disliking a review. The asset reviews will be filtered based on its popularity and date added.
Taxonomy support	This allows - The Admin to define Taxonomy hierarchies in the ES Management Console. The Publisher to apply Taxonomies to various assets. The Store users to filter assets using the available Taxonomies.
Subscribed assets corner	The My Bookmarks section in the Store provides a personalized corner to display subscribed assets.
Asset Management	The following are the tasks entailed in asset management, that is carried out via the WSO2 ES Publisher: Adding a new asset based on the available asset types. Adding a newer version of an already existing asset. Editing an asset. Viewing asset details. Deleting an asset based on the asset lifecycle state and your user roles. Promoting and demoting an asset in the asset lifecycle based on your user role. Viewing historical views of asset lifecycle updates. For more information see, Working with the Publisher.
User Management	Ability to manage the WSO2 ES users together with their assigned roles.
Connect and Scale	Connect to the enterprise user stores to provide access to the existing user bases. Single-Sign on for the Store and Publisher. Clustered deployment for high availability and scalability.