Important: Deprecating old WebView — Publish failed error
New pages
Jump to navigation
Jump to search
- 13:32, 22 May 2025 Import Power Apps to Woodford (hist | edit) [3,216 bytes] Jzambor (talk | contribs) (Created page with "Showcase Resco mobile experience without Woodford knowledge. You can '''convert model-driven apps from your Power Platform or Dynamics organizations into Resco app projects''' in a few easy clicks. Whether you are a partner who wants to prepare a quick demo in the customer environment or a Power Platform admin who wants to try Resco without deep-diving into our app project designer tools, the option to quickly convert model-driven apps can save you a lot of time. __TOC_...")
- 08:50, 19 May 2025 Releases/Fall 2025 (hist | edit) [774 bytes] Jzambor (talk | contribs) (Created page with "{{Releases TOC}} {{WIP}} The 18.2 / Fall 2025 release is {{Popup|planned|The apps are released first (gradual rollout). The server part follows within a few days.}} for '''September 2025'''. Find the '''download''' links for the latest preview version on the '''Preview page'''. == Questionnaire Player Gen 2 == New generation of questionnaires is available for a limited preview. See Questionnaire Player Gen 2 for more informat...")
- 12:05, 14 May 2025 Questionnaire Player Gen 2 (hist | edit) [10,802 bytes] Jzambor (talk | contribs) (Created page with "Coming soon.")
- 08:41, 9 May 2025 Resco Cloud roles and permissions (hist | edit) [3,391 bytes] Jzambor (talk | contribs) (Created page with "{{Admin TOC}} The following document lists the user roles necessary for performing various administrative tasks with Resco Cloud. {| class="wikitable" |+ Definition of terms used in the tables below |- | U || At least user access is required |- | B || At least Business Unit access is required |- | O || Organization access is required |- | <nowiki>U | ... | O</nowiki> || Can be from User to Organization and depends on requirements and max access rights |- | <nowiki>B...")
- 10:42, 24 April 2025 Deep dive: Aggregate questions in repeating groups (hist | edit) [5,929 bytes] Jzambor (talk | contribs) (Created page with "{{WIP}} In this guide, we will demonstrate how a custom reusable JavaScript function can be used from Resco rules to add new functionality to Resco questionnaires. This show the pattern how developers can build libraries of reusable functions that can be used from low-code rules by functional consultants or business users to enrich questionnaires with complex behavior. The example shows how rules and custom JavaScript code can work together to '''calculate total value o...")
- 07:18, 9 April 2025 InspConverter (hist | edit) [64,189 bytes] Jzambor (talk | contribs) (Created page with "{{WIP}} InspConverter is a modified version of Resco Mobile CRM that can convert existing questionnaire answers to modern format: * Change answer format from record-based to JSON. * Convert template-independent questionnaires into template-dependent. It is only available for Windows devices. InspConverter is available on demand: contact Resco support if you are interested. == Why convert questionnaires == Early questionnaire answer formats are prone to generate a lot...")
- 14:52, 8 April 2025 Deep dive: Shopping cart with barcode scanning (hist | edit) [5,113 bytes] Jzambor (talk | contribs) (Created page with "One standard feature of applications dedicated to the sales process is adding items to a basket. For selected entities used in the process, Resco Mobile CRM comes with a special multi-lookup form (sometimes called "shopping basket") to manage items in the list. In this form, products are on the left, and line items are on the right. This behavior is hardcoded and cannot be enabled for other entities. See Resco_Field_Sales%2B#Special_behavior_of_child_lists|Resco Field...")
- 11:55, 14 March 2025 PCF Configuration Tool (hist | edit) [4,134 bytes] Marek Rodak (talk | contribs) (Created page with "{{WIP}} PCF Configuration Tool is designed to assist users in configuring custom code components that require a JSON definition. These components have a predefined JSON schema that outlines their functionality. The PCF Configurator provides a user-friendly interface, allowing users to input information into this JSON schema without needing to work directly with JSON. ==")
- 12:54, 3 March 2025 Tree definition (hist | edit) [5,029 bytes] Marek Rodak (talk | contribs) (Created page with "==Tree-based components== {{WIP}} Tree-based components provide different ways to visualize hierarchical relationships between records. These components share a common JSON configuration, which defines how records are related. {| class="wikitable" ! Component !! Description |- | '''Tree View''' || Displays hierarchical data as a list with expandable nodes. |- | '''Hierarchy Control''' || Provides a graphical visualization of hierarchical relationships. |- | '''Tree Look...") originally created as "Hierarchy definition"