News

Documentation Updates: APIs, Data Storage, Header, Footer, Login/Logout, and More

Update type: Unqork Platform Documentation
Documentation Updates: APIs, Data Storage, Header, Footer, Login/Logout, and More

Each month, we share with you the latest additions and updates to our Unqork Platform Documentation. Stay up-to-date and review the latest information to keep your skills sharp. 

You can find each of these articles and guides in our Documentation Hub which is linked in the navigation menu and included in federated search here on the Community Hub, or by clicking the Help menu within the Unqork platform (video overview).


New Documentation

  • APIs: Connecting Your Apps - Detailed overview of using APIs with Unqork.
     
  • Data Storage - Article within work-in-progress Best Practices course on application performance
    • This course is based on our ongoing 8-part Technically Speaking summer series on YouTube. 
    • Visit the Community Hub home page or Events calendar for upcoming topics and dates. 
       
  • Unqork Sunsetting Process - Learn about what sunsetting is and the positive impact it has on Creators.

Updated Documentation

  • Clarifications on Output Types for Decisions Component & Logic Components - Input & Output Types
    • The "page" & "pageOpen" Output Types only accept values that are URLs or paths. 
    • The “reset” Output Type resets the Disabled, Editable, Hidden, and Required settings of a component to their original values.
       
  • Clarifications on module settings for Header ModuleFooter ModuleLogin Module, and Logout Module.
    • If you are also using the application setting and functionality of the Header and Footer Modules, you must set the Module Permissions of the application’s Logout Module, Header Module, and Footer Module to "Allow Access to Anonymous Users" and provide Read-Only access to Anonymous Users.
       
  • Clarifications added to Introduction to Applications
    • When writing (create/update) to Unqork submissions as a non-Administrator Express role, the Property IDs being saved must be present as a component somewhere within the module or application where the submission will be written to.
    • When writing to Unqork submissions, Super-Users (Admins with Full Submission Access, pre-built Administrator role) behave differently than non-Admins; superseding RBAC controls on which Property IDs can be written to Unqork submissions. This means that Super-Users can write Property IDs to a module even if they Property ID does not exist on the module.
       
  • Significant updates to reflect platform UI enhancements for Chart Component, Table Component, and TEXTJOIN Formula
     
  • Significant updates to improve styling and consistency (matching other articles) for ViewGrid ComponentData Mapper Component, and Plug-In Component.
     
  • Multi-Select Dropdown Component - minor correction in the Data Reference Key scenario.
Be the first to answer!