Create a RobinSkill Output

The purpose of RobinSkill Outputs are designing what data is displayed in the Robin application.


A RobinSkill Connection is required to create a RobinSkill Output.

Open Hero_Flow.Create an Output for a RobinSkill in Hero_Flow

  1. Click Outputs from the menu on the left.

  2. Click Create New Output.

  3. Give the Output a name and select your RobinSkill Connection.
    • Enter a name for the Robin Skill.
    • Enter a description for the Robin Skill. 
    • Select the skill status:
      • Published - Appears in the Robin application.
      • Unpublished -  Does not appear in the Robin application.
    • Select the Robin Output's schema version.
    • Enter the field names under the field mapping table.
    • Click Next.



  4. The task list editor defines the headers displayed for each task. These headers are sortable in the Robin application to allow for better organization and priorities. 
    At least one table header must be selected with a maximum of six.
    • Under Tuple fields, select the tuple fields to be used as Robin task list table headers.
    • Under Robin 'Task List' table headers, enter a title to be displayed in as a header for each field.
    • Click Next.


  5. The filters editor defines which Robin Tasks are displayed for specific Robin users. This feature also prevents Robin users from seeing tasks assigned to other teammates.
    • Select a field name for Robin users.
    • Select the filter type for each field:
      • Equals - The field value is the same as the selected filter value.
      • Not Equals - The field value is not the same as the selected filter value.
    • Select the filter values:
      • Empty - The task lists displays tasks unassigned to a specific user.
      • Robin user in Context - The task list displays assigned tasks to the user in context in Robin.
      • Empty AND Robin user in Context - The task list displays both tasked assigned to the user as well as unassigned tasks.
    • Mark the Read Only box to disable the ability to make changes to this filter by the user in the Robin application. 
    • Click Next.


  6. The schema editor defines how each field box is displayed and how they operate. 
    • Select the UI type for each field. (Based on the data type of the field.)
    • Select the editability for each field.
      • Read only - The data in read only fields are for display only and cannot be edited.
      • Optional - The data in optional fields can be edited. A task can be completed even if the field remains empty.
      • Required -  The data in required fields can be edited. A task cannot be completed if the field remains empty.
    • Click Next.




    Robin Schemas Informational Chart by Value Type


  7. The layout editor defines where each field box is displayed in the Robin application and how large the fields are.
    • Drag and drop each of the field names on the left into the layout editor to assign where each field is displayed in the Robin application.
      • Up to four fields and be added to each line.
      • Fields can be extended horizontally to take multiple slots on the same line or vertically to take up multiple slots on separate lines. |
    • At the top of the editor, select a task header.
    • If needed, add custom components
    • Click Next.



  8. Select the users that have access to the Robin Skill.
    • One or more users can be selected to have access to the Robin Skill.
    • The Hero_Flow administrator has access to the Robin_Skill by default.
    • Click Save to finish saving the RobinSkill Output.

        

Access the Robin Application

In a web browser address bar, type: <Your Hero_Flow URL>/robin-app

After creating a RobinSkill Output, the skill is active in the Robin application. Opening and logging into the Robin application displays the skill name and the task headers. No data populates the skill until it has been used within a Flow.

Learn more in the Robin User's Guide.

Robin Schemas Informational Chart by Value Type

Value data typeUI typeHTML form in RobinValidation behavior in Robin

BIG DECIMAL

  • Decimal number
  • Text field
  • Cannot except string values
  • Accepts negative values
BINARY
  • File
  • Document Review
  • Preview image of file
    • Read only
    • Downloadable
  • Full image of file displayable on click.
    • Read only
    • Downloadable

BOOLEAN
  • Checkbox
  • Select
  • Radio Button
  • Checkbox
  • Dropdown and Radio button
    • Options: True / False

DATE_TIME
  • Date Field
  • Date Time Field
  • Date field w/ calendar selector
    • "Date Field" sets time at midnight server time.
    • "Date Field" does not display a time even if the tuple contains a time value.
  • Date field w/ calendar and time selector
    • "Date Time Field" sets time at midnight server time if the tuple does not contain a time value.
    • "Date Time Field" has the following time zone options
      • Server Time Zone (Time zone of the Hero_Flow server)
      • UTC (Universal Time Coordinated)
      • Robin User's Local (as specified in the user's browser)
  • Date Time Field requires two columns in the layout.
  • Cannot except invalid dates.
DOUBLE
  • Decimal number
  • Text field
  • Cannot except string values
  • Accepts negative values
LIST
  • Select
  • Checkbox
  • Radio Option
  • Multiple Select
  • Drop-down (single selection)
  • Checkbox (multiple selection)
  • Radio button (single selection)
  • Drop-down (multiple selection)
  • SELECT and MULTI SELECT can be set to accept custom values
LONG
  • Whole number
  • Text field
  • Cannot except string values
  • Cannot except decimal values
  • Accepts negative values
STRING
  • Text Field
  • Text Area
  • Table
  • Text field
  • Text area
  • Table
    • See JSON table structure  
    • Table options:

      • Add row above or below the selected row.
      • Exclude or include a row.
    • The Table component requires four rows and four columns in the layout.

JSON Table Structure

 JSON table structure
{ 
	"table": { 
		"columns": [ 
			{ 
				"name": "key-name-in-rows-data", 
            	"label": "Column header in UI" 
			}, 
       		{ 
				"name": "description", 
				"label": "Description" 
			} 
		], 
		"rows": [ 
			{ 
				"data": { 
					"key-name-in-rows-data": "Value 1", 
					"description": "Value Description" 
				}, 
				"meta": { 
					"excluded": true // If this row is removed by robin user 
					"added": true // If this row is new and added by robin user 
				} 
			} 	
		] 
	} 
}


LIST UI types (Select and Multi Select) can be set to accept custom values entered by the Robin user or the automation designer can add default values from a field.

To allow custom values from Robin business users:

  • Click the gear icon next to the LIST data type field and mark the Allow Custom Values box. 

To add a default value field to the list of options:

  • Click the gear icon next to the LIST data type field and select a field from the drop-down menu.