Difference between revisions of "Applications Page Manual 3.0"
(→Blocks) |
|||
| Line 18: | Line 18: | ||
== Blocks == | == Blocks == | ||
| − | === | + | === Applications === |
---- | ---- | ||
[[File:ApplicationsMainBlock_3.png|1000px|center|thumb|Applications information]] | [[File:ApplicationsMainBlock_3.png|1000px|center|thumb|Applications information]] | ||
| Line 44: | Line 44: | ||
! style="text-align:left;border-left:5px solid red;" | Consumer Secret | ! style="text-align:left;border-left:5px solid red;" | Consumer Secret | ||
| oAuth Consumer Secret provided. The authentication process consist of two credentials, one of them is the Consumer Secret. | | oAuth Consumer Secret provided. The authentication process consist of two credentials, one of them is the Consumer Secret. | ||
| + | | | ||
| + | * Mandatory | ||
| + | |- | ||
| + | ! style="text-align:left;border-left:5px solid red;" | Client IP in token | ||
| + | | Pending. | ||
| | | | ||
* Mandatory | * Mandatory | ||
| Line 54: | Line 59: | ||
! style="text-align:left;" | Device Type | ! style="text-align:left;" | Device Type | ||
| Device Type associated with this Application. Can also be managed in the [[Device_Types_Page_Manual_3.0#Applications|Device Type page Application management block]]. | | Device Type associated with this Application. Can also be managed in the [[Device_Types_Page_Manual_3.0#Applications|Device Type page Application management block]]. | ||
| − | | - | + | |- |
| + | ! style="text-align:left;" | API HUB Version | ||
| + | | Pending. | ||
| + | |- | ||
|} | |} | ||
<br /> | <br /> | ||
| + | |||
== Actions == | == Actions == | ||
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 12:56, 21 April 2022
Access to this menu in Betools through: 
Commons > Applications
Contents
This section allows to manage the different applications and their credentials that are enabled in the platform. Applications are created when creating new device types
Name - Given name to Application. Creation Date - Datetime of the Application creation. Owner - Name of the creator. Consumer Key - Consumer Secret - Active - -
Blocks
Applications
| Field | Description | Restrictions |
|---|---|---|
| Name | Given name to Application. |
|
| Owner | Operator that created this item. |
|
| Consumer Key | oAuth Consumer Key provided. The authentication process consist of two credentials, one of them is the Consumer Key. |
|
| Consumer Secret | oAuth Consumer Secret provided. The authentication process consist of two credentials, one of them is the Consumer Secret. |
|
| Client IP in token | Pending. |
|
| Active | Allows to enable or disable this application. |
|
| Device Type | Device Type associated with this Application. Can also be managed in the Device Type page Application management block. | |
| API HUB Version | Pending. |
Actions
| Create | Edit | Edit in List | Bulk Edit | Copy | Copy with Relateds | Delete |
|---|---|---|---|---|---|---|
 |
|
 |
|
|
|
|
Create
OB Administrators and Administrators can manage the list of applications.
- Use the
button to create an empty application. - Fill all the required information.
- Once finished, save changes by using the
button.
Edit
Application edition is enabled for operators. It can be used to modify some existing application information. Once finished modifying the information, save changes by using the 
button in the edit page.
Edit in List
Edit in list is not enabled for this page.
Bulk Edit
Bulk Edit is enabled in this page, allowing you to modify several items at the same time. However, not all the relateds blocks will be available for performing a bulk edit operation. The blocks available are:
- Basic information
Copy
Copy is enabled in this page. Using the 
button, you will be able to clone the basic information from the application into a new application.
Once the application is copied, review that all the fields have been copied properly and press Save button.
Copy with relateds
Copy is enabled for this page and has the same behavior as Copy button.
Delete
Applications can be deleted by the operator using the 
button. A confirmation popup will be shown before excluding it.
