Authorization with x-api-key should be sent via header. If required you may instead use the query string parameter apikey={KEY}
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"2247991","collectionId":"ae24798c-758d-44b1-8326-334014a1ddf7","publishedId":"SVtR1pjr","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"EF5B25"},"publishDate":"2024-09-24T03:07:26.000Z"},"item":[{"name":"Search","item":[{"name":"Search","id":"33ee5142-6ff7-4886-bcff-dfd15fb007df","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://help.livepro.com.au/livepro-api/search?query=test&limit=5&start=0&outputformat=json&type_description=Document Note&future_workflow_status_description=Published&search_mode=neural&source=genai&options=content_only_markdown","description":"Search will query livepro based on a search term to find articles that relate.
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}},"urlObject":{"protocol":"https","path":["livepro-api","search"],"host":["help","livepro","com","au"],"query":[{"description":{"content":"The term that you want to search livepro for
\n","type":"text/plain"},"key":"query","value":"test"},{"description":{"content":"The maximum number of records to return, the default if left blank will be 25
\n","type":"text/plain"},"key":"limit","value":"5"},{"description":{"content":"The offset to start searching from(used for pagination)
\n","type":"text/plain"},"key":"start","value":"0"},{"description":{"content":"The format in which results should be returned, can be json or html
\n","type":"text/plain"},"key":"outputformat","value":"json"},{"description":{"content":"The knowledge object types to include in the query, for multiple types seperate with a comma
\n","type":"text/plain"},"key":"type_description","value":"Document Note"},{"description":{"content":"The workflow statuses that show appear in search results, for multiple results seperate by comma
\n","type":"text/plain"},"key":"future_workflow_status_description","value":"Published"},{"description":{"content":"The type of search to execute. Options are \"neural\" for hybrid search or \"keyword\" for keyword search (default).
\n","type":"text/plain"},"key":"search_mode","value":"neural"},{"description":{"content":"The search source type. The value \"genai\" forces search results to include article content.
\n","type":"text/plain"},"key":"source","value":"genai"},{"description":{"content":"Only to be used when source=genai, forces article content to be formatted as markdown rather than html. For content_only_markdown tables will still be included but with content_only_markdown_strict no html remains.
\n","type":"text/plain"},"key":"options","value":"content_only_markdown"}],"variable":[]}},"response":[{"id":"a17cf879-3b10-451f-9ed9-9801d5fc061e","name":"General search","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"8850fdc718e5da1e86ed4a8fe23f0c73","type":"text"}],"url":{"raw":"https://help.livepro.com.au/livepro-api/search?query=document note&limit=5&start=0&outputformat=json&future_workflow_status_description=Published","protocol":"https","host":["help","livepro","com","au"],"path":["livepro-api","search"],"query":[{"key":"query","value":"document note","description":"Searching for \"document note\""},{"key":"limit","value":"5","description":"Return 5 records"},{"key":"start","value":"0","description":"Start at first record"},{"key":"outputformat","value":"json","description":"Format as JSON"},{"key":"future_workflow_status_description","value":"Published","description":"Search only published records"}]}},"_postman_previewlanguage":"json","header":null,"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"parameters\": {\n \"query\": \"document note\",\n \"limit\": \"5\",\n \"start\": \"0\",\n \"outputformat\": \"json\",\n \"apikey\": \"8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"future_workflow_status_description\": \"Published\",\n \"source\": \"api\"\n },\n \"total\": 24,\n \"records\": [{\n \"id\": \"4196\",\n \"version_id\": \"32414\",\n \"title\": \"How to Create a Document Note\",\n \"summary\": \"Step by step instructions on how to create a document note\",\n \"type\": \"documentnote\",\n \"url\": \"https:\\/\\/help.livepro.com.au\\/livepro-api\\/read?outputformat=json&id=4196&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https:\\/\\/help.livepro.com.au\\/goto\\/how-to-create-a-document-note\",\n \"version\": \"1.76\",\n \"category\": \"Creating Knowledge\",\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2021-02-11 12:33:12\",\n \"search_display_score\": \"100\",\n \"search_server_score\": 377.6573\n }, {\n \"id\": \"3257\",\n \"version_id\": \"29563\",\n \"title\": \"Document Notes - Features\",\n \"summary\": \"Features of a document note\",\n \"type\": \"documentnote\",\n \"url\": \"https:\\/\\/help.livepro.com.au\\/livepro-api\\/read?outputformat=json&id=3257&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https:\\/\\/help.livepro.com.au\\/goto\\/document-notes-features\",\n \"version\": \"1.16\",\n \"category\": \"Multiple\",\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2020-04-15 11:27:49\",\n \"search_display_score\": \"72\",\n \"search_server_score\": 272.91934\n }, {\n \"id\": \"9138\",\n \"version_id\": \"33012\",\n \"title\": \"Embedding a Document Note into another Knowledge Object (BETA)\",\n \"summary\": \"How to embed a document note into another knowledge object\",\n \"type\": \"documentnote\",\n \"url\": \"https:\\/\\/help.livepro.com.au\\/livepro-api\\/read?outputformat=json&id=9138&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https:\\/\\/help.livepro.com.au\\/goto\\/embedding-a-document-note-into-another-knowledge-object\",\n \"version\": \"1.5\",\n \"category\": \"Creating Knowledge\",\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2021-03-04 08:28:22\",\n \"search_display_score\": \"49\",\n \"search_server_score\": 184.92438\n }, {\n \"id\": \"4383\",\n \"version_id\": \"32419\",\n \"title\": \"Knowledge Object Header Fields\",\n \"summary\": \"Explanation of the standard header fields in all knowledge objects\",\n \"type\": \"documentnote\",\n \"url\": \"https:\\/\\/help.livepro.com.au\\/livepro-api\\/read?outputformat=json&id=4383&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https:\\/\\/help.livepro.com.au\\/goto\\/knowledge-object-header-fields\",\n \"version\": \"1.38\",\n \"category\": \"Multiple\",\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2021-02-11 12:40:59\",\n \"search_display_score\": \"34\",\n \"search_server_score\": 129.05927\n }, {\n \"id\": \"4729\",\n \"version_id\": \"31028\",\n \"title\": \"How to Hide a Knowledge Object\",\n \"summary\": \"Step by step instructions on how to hide a knowledge object from the category list\",\n \"type\": \"documentnote\",\n \"url\": \"https:\\/\\/help.livepro.com.au\\/livepro-api\\/read?outputformat=json&id=4729&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https:\\/\\/help.livepro.com.au\\/goto\\/how-to-hide-a-document-note-if-a-hub-is-created\",\n \"version\": \"1.33\",\n \"category\": \"Creating Knowledge\",\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2021-01-28 14:04:19\",\n \"search_display_score\": \"34\",\n \"search_server_score\": 127.77353\n }],\n \"count\": 5\n}"},{"id":"1a3e1c5c-ff38-4870-89cc-4a9e48999edd","name":"Neural search","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"8850fdc718e5da1e86ed4a8fe23f0c73","type":"text"}],"url":{"raw":"https://help.livepro.com.au/livepro-api/search?query=document note&limit=5&start=0&outputformat=json&future_workflow_status_description=Published&search_mode=neural","protocol":"https","host":["help","livepro","com","au"],"path":["livepro-api","search"],"query":[{"key":"query","value":"document note","description":"Searching for \"document note\""},{"key":"limit","value":"5","description":"Return 5 records"},{"key":"start","value":"0","description":"Start at first record"},{"key":"outputformat","value":"json","description":"Format as JSON"},{"key":"future_workflow_status_description","value":"Published"},{"key":"search_mode","value":"neural"}]}},"_postman_previewlanguage":"json","header":null,"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"parameters\": {\n \"query\": \"document note\",\n \"limit\": \"5\",\n \"start\": \"0\",\n \"outputformat\": \"json\",\n \"apikey\": \"8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"future_workflow_status_description\": \"Published\",\n \"source\": \"api\"\n },\n \"total\": 24,\n \"records\": [{\n \"id\": \"4196\",\n \"version_id\": \"32414\",\n \"title\": \"How to Create a Document Note\",\n \"summary\": \"Step by step instructions on how to create a document note\",\n \"type\": \"documentnote\",\n \"url\": \"https:\\/\\/help.livepro.com.au\\/livepro-api\\/read?outputformat=json&id=4196&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https:\\/\\/help.livepro.com.au\\/goto\\/how-to-create-a-document-note\",\n \"version\": \"1.76\",\n \"category\": \"Creating Knowledge\",\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2021-02-11 12:33:12\",\n \"search_display_score\": \"100\",\n \"search_server_score\": 377.6573\n }, {\n \"id\": \"3257\",\n \"version_id\": \"29563\",\n \"title\": \"Document Notes - Features\",\n \"summary\": \"Features of a document note\",\n \"type\": \"documentnote\",\n \"url\": \"https:\\/\\/help.livepro.com.au\\/livepro-api\\/read?outputformat=json&id=3257&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https:\\/\\/help.livepro.com.au\\/goto\\/document-notes-features\",\n \"version\": \"1.16\",\n \"category\": \"Multiple\",\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2020-04-15 11:27:49\",\n \"search_display_score\": \"72\",\n \"search_server_score\": 272.91934\n }, {\n \"id\": \"9138\",\n \"version_id\": \"33012\",\n \"title\": \"Embedding a Document Note into another Knowledge Object (BETA)\",\n \"summary\": \"How to embed a document note into another knowledge object\",\n \"type\": \"documentnote\",\n \"url\": \"https:\\/\\/help.livepro.com.au\\/livepro-api\\/read?outputformat=json&id=9138&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https:\\/\\/help.livepro.com.au\\/goto\\/embedding-a-document-note-into-another-knowledge-object\",\n \"version\": \"1.5\",\n \"category\": \"Creating Knowledge\",\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2021-03-04 08:28:22\",\n \"search_display_score\": \"49\",\n \"search_server_score\": 184.92438\n }, {\n \"id\": \"4383\",\n \"version_id\": \"32419\",\n \"title\": \"Knowledge Object Header Fields\",\n \"summary\": \"Explanation of the standard header fields in all knowledge objects\",\n \"type\": \"documentnote\",\n \"url\": \"https:\\/\\/help.livepro.com.au\\/livepro-api\\/read?outputformat=json&id=4383&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https:\\/\\/help.livepro.com.au\\/goto\\/knowledge-object-header-fields\",\n \"version\": \"1.38\",\n \"category\": \"Multiple\",\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2021-02-11 12:40:59\",\n \"search_display_score\": \"34\",\n \"search_server_score\": 129.05927\n }, {\n \"id\": \"4729\",\n \"version_id\": \"31028\",\n \"title\": \"How to Hide a Knowledge Object\",\n \"summary\": \"Step by step instructions on how to hide a knowledge object from the category list\",\n \"type\": \"documentnote\",\n \"url\": \"https:\\/\\/help.livepro.com.au\\/livepro-api\\/read?outputformat=json&id=4729&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https:\\/\\/help.livepro.com.au\\/goto\\/how-to-hide-a-document-note-if-a-hub-is-created\",\n \"version\": \"1.33\",\n \"category\": \"Creating Knowledge\",\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2021-01-28 14:04:19\",\n \"search_display_score\": \"34\",\n \"search_server_score\": 127.77353\n }],\n \"count\": 5\n}"},{"id":"89505546-f3fd-4b98-bdbb-16c890accd04","name":"LLM search","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://help.livepro.com.au/livepro-api/search?query=test&outputformat=json&search_mode=neural&source=genai&options=content_only_markdown","protocol":"https","host":["help","livepro","com","au"],"path":["livepro-api","search"],"query":[{"key":"query","value":"test","description":"The term that you want to search livepro for"},{"key":"limit","value":"5","description":"The maximum number of records to return, the default if left blank will be 25","disabled":true},{"key":"start","value":"0","description":"The offset to start searching from(used for pagination)","disabled":true},{"key":"outputformat","value":"json","description":"The format in which results should be returned, can be json or html"},{"key":"type_description","value":"Document Note","description":"The knowledge object types to include in the query, for multiple types seperate with a comma","disabled":true},{"key":"future_workflow_status_description","value":"Published","description":"The workflow statuses that show appear in search results, for multiple results seperate by comma","disabled":true},{"key":"search_mode","value":"neural","description":"The type of search to execute. Options are \"neural\" for hybrid search or \"keyword\" for keyword search (default)."},{"key":"source","value":"genai","description":"The search source type. The value \"genai\" forces search results to include article content."},{"key":"options","value":"content_only_markdown","description":"Only to be used when source=genai, forces article content to be formatted as markdown rather than html. For content_only_markdown tables will still be included but with content_only_markdown_strict no html remains."}]}},"status":"OK","code":200,"_postman_previewlanguage":null,"header":null,"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"knowledge_objects\": [\n {\n \"id\": 6377,\n \"title\": \"Creating a Quiz\",\n \"content\": \"1. Click  in the top navigation panel\\n2. From the pop-up, select the following: \\n - **Type**: Quiz\\n - **Workflow**: Default\\n3. Select ****\\n4. Populate the Details tab \\n - **Categories**: Make sure to save your Quiz to a Distribution List. Users with access to the Distribution List/s will be able to access it. You may publish the in more than one category.\\nQuiz Overview\\nOnce you have completed the Details tab you should now complete the **Overview** Tab.\\n**Overview Tab**\\nThis is the first page the user will see when they enter the quiz. Use the [WYSIWYG Editor](/view/4195 \\\"WYSIWYG Editor\\\") to create text, images, links, and attachments to give the user an introduction to the Quiz.\\n
|  | **Tip**: The description is an ideal place to link to reference materials for users. Use the insert resource button to link to internal livepro resources, or the insert/edit link button to link to external web pages. For example, you might say \\\"Before completing this quiz, please make sure you have read and understood the cancellations process changes\\\" |
\\nNext, select the parameters for the Quiz. These include:\\n- **Questions per attempt** - Select the number of questions the user will be required to answer per attempt. Leaving this field blank will mean the user will need to answer every question.\\n- **Maximum user attempts** - Enter the maximum number of times the user can attempt the Quiz.\\n- **Time limit per question** - Enter a time in minutes or seconds if you wish to impose time limits on each question. Leaving this blank wo not impose a time limit for the Quiz.\\n- **Randomize questions** - Selecting this option will present your quiz questions in random order each time the quiz is attempted. Select this option if you have limited the Questions Per Attempt to display different questions each time a user attempts the quiz.\\n- **Detailed results** - Selecting this option will provide the user with additional information on which questions were answered correctly or incorrectly.\\n\\nQuestions Tab\\nOnce you have completed the Quiz Details and Overview Tabs, you can create your questions.\\n1. In the **Questions** tab, add a new question by clicking the  **Create Question** button\\n2. In the **Type** column, select the type of question: \\n
| \\n - **Multiple Choice** - The user will be presented with multiple answers. By default, only one answer can be selected as correct. Use the Multiple Correct Answer toggle to allow multiple answers to be selected.\\n - **Yes or No** - Users can select Yes or No to answer this Question.\\n - **True or False** - Users can select True or False to answer this Question.\\n - **Free Text** - The user must manually type in the answer to the question. Note: provide the users with the format they should enter their answer in e.g. \\\"Enter date in the following format 10/10/2010\\\". Spelling errors and synonyms will eb marked as incorrect unless they are added as an answer to this Question.\\n |
|
|
|
|
\\n3. Enter your question in the WYSIWYG editor under the **Question** column.\\n4. Once you have input your questions, you can add the answers before moving on to the next question.\\n**Note:** Select the **Randomize Answers** toggle to have the answers presented in a different order for each user attempt.\\n\\nAnswers\\nOnce you have input your questions, you can add the answers before moving on to the next question.\\n1. For **Multiple Choice** and **Free Text** question types**,** click the **+Add Answer** link. Note: To enable multiple answers, switch on the toggle button next to **Multiple Correct Answers**.\\n2. In the Edit Answer pop-up box, enter the answer to the question. Note: If the answer you have entered is correct, tick the box titled **Correct Answer.** No tick box for Free Text questions.\\n3. For **Yes or No** and **True or False** question types, select the correct answer from the **Correct Answer** dropdown.\\n4. **Save** the answers\\n5. Repeat the above steps and add in incorrect answers\\nPublish\\n1. Set your Quiz status to **Published** under the Details Tab.\\n2. Click the **Save** button at the top-right corner of the Create Quiz window\\n3. In the **Save Knowledge** pop-up box, you can enter your comments. These comments are visible to other authors in the history view and can provide information on why and what changes were made.\\n4. Click .\\nUsers in the chosen Distribution List will now be able to navigate to the Quiz menu and run the Quiz.\\nReporting on Results\\nOnce users have run the quiz, you have multiple options to report on their results\\n**Option 1 - Quiz Menu**\\n1. As an author or admin, locate the quiz you created and select the '**reporting**' button on the navigation bar\\n2. Select the '**quiz results**' tab and run the report\\n3. To see further information, you can double click on the user to continue to drill down and see more information about individual attempts\\n**Option 2 - Dashboards**\\n1. Navigate to the reporting dashboards\\n2. Choose the hamburger icon at the top left and navigate to **browse --> reports**\\n3. Locate the Quiz reports in the list
\\n\"\n },\n {\n \"id\": 9296,\n \"title\": \"Feature & Improvement Requests\",\n \"content\": \"Understanding livepro's Feature Request and Release Process\\n===========================================================\\nHow Feature Requests Work\\n-------------------------\\nAt livepro, we're constantly working to improve our platform based on your feedback. Understanding how your requests transform into actual features can help you engage more effectively with our development process.\\nWhen you contact us with a feature request, our team initiates a comprehensive evaluation process:\\n1. **Documentation Phase**: We document your request in meticulous detail, capturing not just what you want, but why you need it and how it would integrate into your workflows. This detailed documentation helps our team understand the underlying business needs rather than just the technical specifications.\\n2. **Feasibility Assessment**: Our development specialists evaluate your request against our technical architecture, considering factors such as: \\n - Integration requirements with existing features\\n - Potential impacts on system performance\\n - Security considerations\\n - Compatibility with our development roadmap\\n3. **Ticket Creation and Classification**: Once documented, a formal development ticket is created in our project management system. The ticket includes: \\n - A unique identifier for tracking purposes\\n - Detailed requirements documentation\\n - Priority classification based on client impact and technical complexity\\n - Assignment to appropriate development resources\\n4. **Client Communication**: We maintain transparency throughout the process by notifying you when the feature is confirmed for a future release, including estimated timelines when possible.\\n### Implementation & Testing\\nThe journey from concept to deployment involves several sophisticated stages designed to ensure reliability and performance:\\n#### Development Phase\\nYour requested feature undergoes meticulous development by our specialized team, following a structured process:\\n- **Requirements Analysis**: Our developers first translate business requirements into technical specifications, creating a blueprint for the new feature.\\n- **Design Phase**: The team creates a technical design that outlines how the feature will be built and integrated into the existing system architecture.\\n- **Coding**: Using modern development methodologies, our engineers write clean, efficient code that implements the design while adhering to our coding standards.\\n- **Code Review**: Senior developers review all code for quality, security, and adherence to best practices before it moves to testing.\\n#### Quality Assurance / Testing Process\\nBefore any feature reaches your livepro environment, it undergoes rigorous multi-stage testing:\\n- **Unit Testing**: Individual components are tested in isolation to verify their fundamental functionality.\\n- **Integration Testing**: Components are tested together to ensure they work harmoniously with existing features.\\n- **System Testing**: The complete feature is tested within a production-like environment to validate end-to-end functionality.\\n- **User Acceptance Testing**: Our internal teams validate the feature from an end-user perspective.\\n- **Performance Testing**: For features that may impact system performance, we conduct load and stress testing to ensure optimal operation under various conditions.\\n#### Deployment Preparation\\nOnce testing is complete, we prepare for a smooth deployment:\\n- Documentation updates for users and administrators\\n- Creation of training materials where needed\\n- Final quality assurance checks\\n- Release notes preparation\\nFrequently Asked Questions\\n--------------------------\\n### How long will it take for my requested feature to be implemented?\\nUnderstanding implementation timelines helps set realistic expectations about when you might see your requested features in production. Several factors influence development schedules:\\n#### Prioritization Factors\\n- **Client Demand**: Features requested by multiple clients naturally receive higher priority, as they represent broader market needs. When many clients identify the same pain point or opportunity, we can be confident the development investment will benefit a significant portion of our user base.\\n- **Strategic Alignment**: Features that align with our product roadmap and strategic vision may be accelerated. We continuously balance client-specific requests with our overall product evolution strategy.\\n- **Complexity Assessment**: The technical complexity of a feature dramatically impacts development time: \\n - Simple UI changes or minor functionality adjustments might require minimal development effort\\n - Features requiring new database structures or integration with third-party services typically need moderate development time\\n - Major system architecture changes or entirely new modules with complex logic can require extensive development resources\\n- **Resource Allocation**: Development capacity is carefully managed across maintenance, improvements, and new feature development. Large-scale features may be broken into smaller, manageable components that can be developed and released incrementally.\\n#### Typical Timelines\\nBased on these factors, once a request receives prioritization, you can expect:\\n- **Small enhancements**: 2-6 weeks\\n- **Medium-complexity features**: 1-3 months\\n- **Large-scale features**: 3+ months\\nThese timelines represent development through final release, including all testing phases. We prioritize quality over speed to ensure that new features meet our high standards for reliability and performance.\\n### Why are fixes deployed faster than new features?\\nYou may notice that when an existing feature encounters an issue, our response time is considerably faster than for new feature development. This difference reflects fundamental aspects of software development and maintenance:\\n#### Technical Considerations\\n- **Scope Differences**: Bug fixes typically target a specific, isolated problem within existing code, while new features require entirely new designs, code structures, and integration points. This difference in scope naturally leads to different timelines.\\n- **Risk Assessment**: Fixes generally pose lower implementation risks than new features because: \\n - The code structure already exists and is understood by the development team\\n - The feature's integration points with other system components are established\\n - Testing can focus on specific functionality rather than wide-ranging impacts\\n- **Deployment Methodology**: We employ different deployment approaches based on the type of change: \\n - Critical fixes may be deployed through our hotfix process, allowing for rapid resolution outside the normal release cycle\\n - Non-critical fixes are typically bundled into scheduled maintenance releases\\n - New features generally require more extensive testing and are reserved for major version releases\\n#### Prioritization Logic\\nWe maintain a balanced approach to development priorities, where:\\n- **Service Restoration**: Resolving issues with existing functionality takes precedence because these affect capabilities your team already relies on and has incorporated into workflows\\n- **Contractual Obligations**: Maintaining the quality and availability of existing features is part of our core service commitment\\n- **Resource Efficiency**: Fixing issues in existing code typically requires fewer developer hours than building entirely new functionality, allowing us to address more client needs in a given timeframe\\nThis approach ensures we maintain a stable, reliable platform while continuously evolving to meet new needs.\\nStaying Informed\\n----------------\\nEffective change management requires proactive communication. We provide multiple channels to keep you informed about upcoming changes, new features, and improvements to the livepro platform:\\n### Communication Channels\\n- **Email Notifications**: We send detailed release notes via email before each update, including: \\n - Feature descriptions with screenshots and usage examples\\n - Changes to existing functionality\\n - Known issues and workarounds\\n - Implementation timelines\\n - Recommended preparation steps\\n- **Communities Page**: Our client community serves as a comprehensive knowledge base and communication hub: \\n - The \\\"Product Updates\\\" category provides chronological access to all release information\\n - Feature previews offer early glimpses of upcoming functionality\\n - Discussion threads allow you to ask questions about specific updates\\n - Success stories showcase how other clients have implemented new features\\n### Advance Notice Commitments\\n**For Major Releases:**\\n- **High-Impact Changes** (UI overhauls, workflow changes, API modifications): \\n - 2-4 weeks notice\\n - Detailed communication plan with documentation\\n- **Low-Impact or Opt-In Features** (no workflow disruption): \\n - 1 week notice\\n**For Minor/Bug Fix Releases:**\\n- **Bug Fixes**: \\n - Pushed out when ready to deploy\\n - Updates provided via release notes on help site\\nHow to Submit Effective Feature Requests\\n----------------------------------------\\nThe quality and specificity of your feature requests significantly influence how quickly we can evaluate, prioritize, and implement them. Here are guidelines for submitting requests that provide our team with the information needed for efficient processing:\\n### Elements of an Effective Feature Request\\n1. **Clear Business Objective**: Explain the business goal you're trying to achieve, not just the technical implementation you envision. Understanding the \\\"why\\\" helps us design the most appropriate solution.\\n2. **Use Case Scenarios**: Describe specific situations where this feature would be used and how it would improve your workflows. Include: \\n - Who would use the feature (roles/departments)\\n - When they would use it (at what point in existing processes)\\n - What outcome they expect\\n3. **Impact Assessment**: Help us understand the significance of this feature by explaining: \\n - How many users would benefit\\n - What processes would be improved\\n - Quantifiable benefits (time savings, error reduction, etc.)\\n - Current workarounds and their limitations\\n4. **Priority Indication**: While we evaluate all requests independently, your input on urgency helps us understand your needs: \\n - Critical: Business operations are significantly impacted without this feature\\n - High: Feature would substantially improve efficiency or capabilities\\n - Medium: Feature would provide notable but not urgent improvements\\n - Low: \\\"Nice-to-have\\\" enhancements\\n5. **Visual Examples**: When applicable, include mockups, screenshots from other systems, or diagrams that illustrate your vision for the feature.\\n### Submission Channels\\n- **Support Email**: Submit detailed feature requests through our support email for formal tracking\\n- **Account Manager**: Discuss strategic feature needs with your Account Manager during review meetings\\n- **User Community**: Post ideas in the \\\"Feature Suggestions\\\" section of our Communities Page to gauge interest from other clients
\\n\"\n },\n {\n \"id\": 9067,\n \"title\": \"Spell-Check\",\n \"content\": \"Spell-Check\\nThe spell-check function is browser based, which means that if spell-check is enabled on your browser, a red squiggly underline will automatically appear under any words that are spelt incorrectly. Grammar is not checked by the browser, however there are many browser add-ons that can be installed to enable this for you.\\nUsing Spell-Check in livepro\\nTo access the suggested spellings of those words, simply **hold down the Ctrl button** and then **right-click** the underlined text.\\n
\\n\"\n },\n {\n \"id\": 9797,\n \"title\": \"Generative Search (AI Overview)\",\n \"content\": \"Generative Search (AI Overview)\\nThe search can work in conjunction with our self-hosted Large Language Model (LLM) to generate answers to queries, rather than just a list of results. To do this accurately, we utilize Retrieval Augmented Generation (RAG) which is industry best practice to generate answers with minimal hallucinations.\\nWhen you query livepro, it searches for relevant articles based on your specific permissions. The AI Overview then generates answers using only these authorized documents in real-time. If your question can't be answered from the available content, we will indicate this to the user, instead of attempting to come up with an answer.\\nSince our system respects permission structures, identical queries from different users may receive different responses based on their assigned roles. This is by design—ensuring information delivery aligns with organizational roles and responsibilities. If you can't find an article through regular search, the AI Overview similarly won't have access to that information when answering your questions.\\nAny updates to knowledge base articles are immediately reflected in responses, maintaining consistent and current information across all system interactions.\\nThe generative search component is a paid add-on, please reach out to your account manager or support team to enable / test this feature.\\n\\nWhere do the answers come from?\\nAt this stage, we only process document notes, source documents and announcements to generate responses, deliberately excluding work instructions. This limitation is strategic rather than technical—while comprehensive, work instructions contain critical steps, exact scripts, and technical details that AI summarization might inadvertently omit or misrepresent. By focusing on informational content first, we ensure the system delivers reliable answers while we develop specialized handling for procedural content that will maintain the integrity and completeness of your work instructions.\\nEnabling AI Overview / Generative Search\\nAI Overview is role based, meaning you can choose which users in your organization have access to this feature (and do some internal testing before making it live). Simply:\\n1. Reach out to our support team or your account manager to have this feature enabled\\n2. Once enabled, as an administrator, navigate to the administration section\\n3. Click '**Roles**'\\n4. Click on the role to enable this feature for and choose **edit**\\n5. Under 'Search Modes', you'll now have the ability to choose '**generative**'\\nSecurity and Technical Information\\nOur AI implementation is securely self-hosted within our AWS infrastructure, operating in a private Virtual Private Cloud (VPC) with strict network access controls that prevent any external communication. The architecture employs end-to-end encryption for all data in transit and at rest. All customer data remains within your geographic boundaries, never leaving your controlled environment, while comprehensive audit logging tracks every interaction. The deployment undergoes regular security assessments, including penetration testing and vulnerability scanning, to maintain compliance with industry standards such as SOC 2 and HIPAA. This fully-isolated implementation ensures that your sensitive information remains protected within your security perimeter at all times.\\n- Self-hosted in tenants AWS region for security\\n- Data does not leave your environment and your content is not used to train the model\\n- We can support different models, however this is subject to the availability of the model in the client region\\n- More technical details can be provided upon request\\nSafeguards\\nOur knowledge management system employs robust safeguards through a Retrieval-Augmented Generation (RAG) architecture that strictly limits responses to information contained within livepro. The system is designed with content boundaries that prevent users from accessing or receiving information outside their authorized scope, ensuring that all responses are grounded exclusively in company-approved documentation. Our implementation includes query filtering that identifies and blocks attempts to circumvent these restrictions, while the retrieval mechanism is configured to only pull from verified internal sources, completely isolating the system from external data. These technical controls work together to maintain data sovereignty, prevent information leakage, and ensure that all AI-generated responses remain consistent with our organization's approved content guidelines.\\nDespite this, users should always verify AI-generated responses against source documentation, as even with these safeguards in place, AI systems may occasionally produce inaccuracies, misinterpretations, or errors despite our best efforts to ensure reliability and accuracy.\\nReporting\\nThe 'Search - Generative' report is available in your Dashboard and will provide the below information. All reports will have all normal filters.\\n- Search date\\n- Search term\\n- User who made search\\n- Generative response provided
\\n\"\n },\n {\n \"id\": 9796,\n \"title\": \"Search\",\n \"content\": \"Understanding Search in livepro\\nSearch is a fundamental feature in livepro that helps users quickly find the information they need. When a user performs a search in livepro, the system scans through the knowledge base to find relevant articles and resources based on the search query. It's important to understand that search results are tied to user permissions, meaning users will only see search results for content they have access to within their assigned categories.\\nThe effectiveness of search depends on how articles are structured, tagged with keywords, and which search mode is configured for different user roles. Understanding how search works will help you optimize your knowledge base and ensure users can find information efficiently.\\nSearch Modes\\nlivepro offers three different search modes that can be configured per user role:\\n**1. Keyword Search**\\nKeyword search is the traditional search method that looks for exact matches of search terms within articles.\\n- All words in the user's query must be present across any field within the knowledge object for it to appear in results\\n- Results are returned based on relevance, which is determined by where the keywords appear in the article\\n- Different fields within articles are weighted differently to prioritize more important matches:\\n
| **Field** | **Weight** |
| **Title** | 10 |
| **Keywords** | 5 |
| **Search Summary** | 1 |
| **Content** | 1 |
\\n**2. Hybrid Search / Natural Language Search (recommended)**\\nHybrid search combines traditional keyword searching with advanced natural language processing to provide more intuitive results. It does this by utilizing a vector database.\\n- This mode integrates both keyword matching and semantic understanding to deliver more comprehensive results\\n- Keywords account for 51% of the overall search score, with semantic relevance making up the remainder\\n- Uses a vector/AI database which helps users find relevant information even when using synonyms or related terms not explicitly listed in keywords\\n- This means content creators don't need to add excessive keywords to articles, as the system can make intelligent connections between search terms and relevant content\\n**3. Generative Search / AI Overview (Additional paid add-on)**\\nGenerative search is an advanced feature that provides AI-generated answers based on knowledge base content.\\n- Utilizes Hybrid search capabilities combined with our self-hosted large language model (LLM)\\n- Instead of just displaying matching articles, this mode generates direct answers to user queries based on relevant content\\n- Helps users get immediate answers without having to read through multiple articles\\n- This is a premium feature that requires additional subscription (not visible by default)\\n- To gain access to Generative Search, please contact support or your account manager\\nMore information regarding the generative search feature (examples / technical info) can be [found here](/view/9797 \\\"Generative Search\\\").\\nAdvanced Search (Boolean)\\nWith the advanced search function, users can drill down their search results using a host of filters and keyword options. The Advanced Search function is accessible by clicking inside the Search field and then selecting  from the dropdown, making it easy to access without being in the way.\\nMore information about advanced search can be [found here.](/view/8968 \\\"Advanced Search\\\")\\nBenefits of Different Search Modes\\nEach search mode offers distinct advantages depending on your organization's needs:\\n- **Keyword Search** is straightforward and works well when users know exactly what they're looking for and use terminology that matches your content.\\n- **Hybrid Search** provides a more flexible experience that accommodates different ways of expressing the same information need, making it easier for users to find relevant content even when they don't use the exact terminology in your articles.\\n- **Generative Search** delivers the most user-friendly experience by directly answering questions, reducing the time users spend searching through articles and increasing productivity.\\nChanging User Search Mode\\nThe search type used is controlled at the role level, meaning different user types can exhibit different search behavior.\\n1. As an admin, access the administration area of your site\\n2. Click '**Roles**'\\n3. Choose the role you'd like to change the search behavior for\\n4. Click on '**Edit**'\\n5. From the '**Search Mode**' drop down, choose the search type\\n6. Select **Save**\\n**Note:** Consider the needs of different user roles when configuring search modes. For example, new users might benefit from Generative Search, while experienced users might prefer Hybrid or Keyword Search for more precise control over results.
\\n\"\n },\n {\n \"id\": 9609,\n \"title\": \"Setup livepro Agent Assist in Genesys Cloud\",\n \"content\": \"\"\n },\n {\n \"id\": 9339,\n \"title\": \"Compare Versions\",\n \"content\": \"Compare Versions\\nlivepro allows you to select any two versions of a Document Note or Work Instruction and quickly identify any content that was added or removed between the two versions. The Compare Versions feature can be easily accessed via the 'Compare Versions' button in the History window for Document Notes and Work Instructions.\\n![]()\\n Any user with 'Edit' or 'Access to History' permissions for Document Notes or Work Instructions will be able to compare between different versions.\\nThe compare version window will display all content that appears in both the To and From versions you selected. Content will be highlighted depending on which version it appears in.\\n
| Text that appears in both versions of the Document Note with paper as normal. | Example Text |
| Text that appears in the earlier 'From' version but not in the later 'To' version will be highlighted in red with a strikethrough. | Example Text |
| Text that appears in the later 'To' version but not in the earlier 'From' version with be highlighted in blue and underlined. | Example Text |
\\nUsing the Compare Versions feature\\n
| 1 | Locate the Document Note or Work Instruction you'd like to compare the versions of. |
| 2 | Select the  '**History**' button. |
| 3 | Select the  '**Compare Versions**' button. |
| 4\\n | A pop-up window will appear.\\n\\nSelect which versions you'd like to compare.\\n |
| 5 | Click  |
| 6\\n | A new popup window will appear, displaying the difference between the two selected versions.\\n**Note:** Work Instructions will appear in 'list view' with all steps displayed consecutively. Any changes made to the order or add/removal of steps will appear as a change in content in this window.\\n |
\\n\"\n },\n {\n \"id\": \"9313\",\n \"title\": \"Run the Tutorial\",\n \"content\": \"livepro Tutorial\\nWhether you're a new user or just need a quick refresher, the Tutorial option is a quick way to familiarise yourself with the basics of livepro.\\nTopics covered by the Tutorial include:\\n- Categories\\n- Page Menu\\n- Feedback\\n- Navigation Bar\\n- Search\\n- Knowledge Object types\\nHow to run the Tutorial\\n
| 1 | In the top right corner of the main livepro screen, Click the blue 'Start Site Tour!' button.\\n | \\n |
| 2 | The Tutorial will begin. |  |
|  | The Tutorial can be stopped at any time by pressing the x button in the top right corner of the current Tutorial popup. |
\\n\"\n },\n {\n \"id\": 4738,\n \"title\": \"See all Knowledge / Listing\",\n \"content\": \"Viewing all Knowledge\\nTo see a complete list of all knowledge in your site, you have two options:\\n- Listing report in the Knowledge Dashboards\\n- 'See all Knowledge' menu located under the search results\\nFinding & Filtering in livepro\\nAs an administrator or author, you can quickly see / filter all knowledge by doing the following:\\n1. Click your cursor into the empty search box\\n2. Select the 'See all Knowledge' button\\n3. All knowledge results will now appear (**note**: you will only be able to see all knowledge your role has access to)\\n\\nFilters Available\\n
| **Knowledge Type** | - Announcement\\n- Document Note\\n- File\\n- Hub\\n- Person\\n- Quiz\\n- Rocket\\n- Work Instruction\\n |
| **Average Score** | The average score of ratings left on knowledge objects by users.\\n- 1\\n- 2\\n- 3\\n- 4\\n- 5\\n |
| **Expired** | Include or exclude knowledge objects that have expired.\\n- No\\n- Yes\\n |
| **Parent Category** | This will display all knowledge objects saved in the selected parent category.\\n |
| **Knowledge Owner** | The currently assigned [Owner of knowledge objects](/view/9421 \\\"Knowledge Owner\\\"). If no Owners are set, this filter will not appear.\\n |
| **Status** | The knowledge could be in a status of:\\n- All (Meaning all of the below selections will be chosen)\\n- Archived\\n- Pending\\n- Published\\nAdditional status may be available depending on your [Workflow](/view/8643 \\\"Workflow\\\")\\n |
| **Review Period** | The review period can be any of the following periods:\\n- All (Meaning all of the below selections will be chosen)\\n- 3 months\\n- 6 months\\n- 9 months\\n- 12 months\\n |
| **Review Date** | The review date will show the following:\\n- All (Meaning all of the below selections will be chosen)\\n- Past due\\n- Review in 14 days\\n- Review in 30 days\\n- Review in 60 days\\n- Review in 90 days\\n |
| **Author** | Filter by knowledge object Author\\n- All (Meaning all of the below selections will be chosen)\\n- Names of authors on your livepro site\\n |
\\n\"\n },\n {\n \"id\": 9417,\n \"title\": \"Filter Tables\",\n \"content\": \"A Search Filter can be attached to an existing table allowing users to quickly search for knowledge within the table. When a search term is entered into the filter bar, all table rows that don’t contain the search term will be hidden, leaving only relevant knowledge displayed to the user. Removing the search term from the filter bar, the table will return to its original state. Insert a new table with a filter into a knowledge object You can use the 'LP Filter Table' Temple to insert a new table into a knowledge object with the filter already attached. If you are already have a table that you want to filter, we recommend inserting the template and copy / pasting the contents of the old table, into the new table. 1 Create or Edit a knowledge object 2 Click the Insert Template button 3 Click the dropdown menu and select 'LP Filter Table' 4 Click OK 5 Template and filter will appear in the WYSIWYG editor. Note: currently, only one filter table can used per article
\\n\"\n },\n {\n \"id\": 4742,\n \"title\": \"Feedback\",\n \"content\": \"Feedback helps you tap into your front line users and keep your content up to date. It is a great way to capture continuous improvement and ideas. There are four types of feedback where users can access to input their comments:\\n| \\n | Selecting the **Feedback** icon on the left navigation bar will allow the user to see all feedback they have lodged or feedback that is assigned to them to action or comment.\\n | | Feedback is now categorised by tabs:\\n- All Active Feedback\\n- My Feedback\\n- Owned Feedback\\n- All Feedback\\nThe default feedback tab shown for users with Read Only permissions is **My Feedback**. For any users with Author or Admin permissions assigned, the default feedback tab shown is **All Active Feedback**\\n | | \\n | There is now a new notification button which will accompany a red dot when:\\n- Feedback is submitted on a knowledge object that you have permission to read/edit\\n- The feedback you have submitted is actioned, updated or closed.\\n- Feedback is assigned to you to action\\n |
\\nGeneral Feedback\\n| This feedback type is not related to any specific content, it may include content suggestions or improvement ideas. The general feedback icon is now located under the user profile.\\n | \\n |
\\nKnowledge Feedback\\n| This feedback is specific to an existing knowledge object and can be found on the navigation bar when browsing any knowledge items. Users may also see this icon , which allows users to view feedback left on this knowledge by other users.\\n | \\n |
\\nRating Feedback\\n| The rating stars are located in the top right-hand corner when viewing a knowledge object that has the [Rating option](/view/4193 \\\"Options Tab\\\") enabled. Ratings allow users to quickly provide feedback on how helpful the knowledge object is. When a rating of 2 or below is selected, a pop-up will appear asking the user to provide more details. Users will see the last rating they selected until the version has had a major update at which point the star ratings is reset.\\nContent authors will see the average score and the number of people who have rated the knowledge object next to the rating stars.\\nRatings can be disabled/enabled on individual knowledge objects as required in the [options tab](/view/4193 \\\"Options Tab\\\").\\n | \\n |
\\nSearch Feedback\\nThis feedback is captured when any user executes a basic or [advanced search](/view/8968 \\\"Advanced Search\\\") where no results are returned. Even if the user doesn't leave feedback at this stage, their search query will still be captured in the reporting.\\n\\nCustomising Feedback\\nThere are several ways to customise feedback in livepro. This helps improve feedback given by users and makes it easier for authors to action it.\\nSome of these options include:\\n- [Customise Feedback Statuses](/view/9216 \\\"Customising Feedback Statuses\\\")\\n- [Send General Feedback to specific Role](/view/9086 \\\"Feedback Segregation\\\")\\n- [Update General, Knowledge and Rating window messages](/view/9373 \\\"Customising the Feedback Window\\\")\\\\*\\n\\\\* This option can only be changed by the livepro support team. Please email our Support Team at for assistance.\\n |
\\n\"\n },\n {\n \"id\": 9072,\n \"title\": \"Web browser compatibility with livepro\",\n \"content\": \"Which web browser can I use to access livepro?\\nlivepro supports the following web browsers.\\n
| \\nMozilla Firefox\\n | \\nMicrosoft Edge\\n | \\nGoogle Chrome\\n |
\\nHow does livepro select which browsers are supported?\\nBefore every major livepro update our Support Team thoroughly tests all livepro functions and features using the latest publicly available version of the browsers above. We recommend using the latest publicly available versions of the web browsers above when using livepro.\\nFor assistance verifying or updating your browser version, please refer to the relevant browser's support site or contact your IT department.\\nPlease note that livepro is no longer supported in Internet Explorer as of 15 June 2022.
\\n\"\n },\n {\n \"id\": 9454,\n \"title\": \"Dynamics 365 Integration\",\n \"content\": \"Microsoft Dynamics 365\\nMicrosoft Dynamics 365 is a Customer Relationship Management program that many customers use to store their customer data and manage client interactions.\\nIf your organisation utilises dynamics, you can embed livepro within your cases / interactions to pop knowledge suggestions straight to an agent (without them needing to search). Likewise, you can allow Dynamics access to livepro data through ingestion, allowing you to use Co-Pilot to generate answers to your customers.\\nPlease see below video for an example.\\n
#### Integrating with Co-Pilot (Ingesting)\\n| Please contact us for steps in setting this up |
|
#### Integrating with an IFrame\\n| Steps\\n- Login to Dynamics365 ensuring you have admin privileges\\n- Click the App you want to customise at the top of the navigation bar e.g. ‘Omnichannel for Customer Service’\\n*A pop-up will display*\\n- Hover over the app name you want to customise\\n- Select the three dots\\n- Choose ‘open in app designer’\\n- On the top left navigation bar, hover over the three dots\\n- Choose ‘switch to classic’\\n*The classic ‘app designer’ window will open*\\n- Under the ‘Case’ entity, click the drop-down arrow\\n- Select the edit pencil against the case form you want to customise\\n- The ‘case’ entity will open in Powerapps\\n- On the top navigation bar, choose ‘Switch to Classic’\\n- You will now see the layout of your existing entity (a ‘case’ in this example)\\n**Adding a livepro iFrame component**\\n- On the top navigation bar, select ‘Insert’\\n- Select ‘IFRAME’ on the navigation bar\\n- Choose the first URL for the old inline view or the second URL for the new UI\\n- Fill out the following: \\n - Name: livepro\\n - URL: <sitedomain>/inline#/search/test e.g. \\n - URL: <sitedomain>/newui/search?query=test e.g \\n - Ensure ‘Pass record object-type code as parameters’ is NOT selected\\n - Label: livepro\\n - Ensure ‘Restrict cross-frame scripting, where supported’ is NOT selected\\n - ‘Visible by Default’ – Selected\\n - ‘Enable for mobile’ – optional\\n- Move the component to where it should sit in the page\\n**Add event to update page case**\\nThis adds the javascript required in the page to automatically find the case details and then pass them through to the livepro iframe.\\n- On the top navigation bar, ensure you’re on the ‘Home’ tab\\n- Click on ‘form properties’\\n- Under ‘Form Libraries’, select ‘Add’\\n- Down the bottom-left, select ‘New’\\n*A new window will open*\\n- Enter the following: \\n - Name: livesearch\\n - Display Name: optional\\n - Description: optional\\n - Type: Script (Jscript)\\n- Select the ‘text editor’ button that appears\\n- Enter the following:\\n```\\nfunction loadSearchForm(executionContext) {\\n var formContext = executionContext.getFormContext();\\n var caseTitle = formContext.getAttribute(\\\"title\\\").getValue();\\n var IFrame = formContext.ui.controls.get(\\\"IFRAME_livepro\\\");\\n var Url = IFrame.getSrc();\\n var params = Url.substr(0, Url.indexOf(\\\"?\\\"));\\n var searchUrl = Url+caseTitle;\\n IFrame.setSrc(searchUrl);\\n}\\n```\\n- Select ‘OK’\\n- Select ‘Save’ on the top navigation bar\\n- Select ‘Publish’ on the top navigation bar \\n Once done, you can now close this page and return to the previous window\\n- The name of the script should now be selected in this list. Select ‘Add’\\n- Under the ‘Event Handlers’ section, click ‘Add’\\n- Under Library, locate in the drop-down the script we just added above\\n- Under function, type \\\"loadSearchForm\\\"\\n- Ensure ‘Enabled’ is selected\\n- Ensure ‘Pass execution context as first parameter’ is selected\\n- Select ‘OK’\\n- Select ‘OK’ again to return to the editor window\\n- Select ‘Save’ on the top left navigation bar\\n- Select ‘Publish’ on the top left navigation bar\\n- Return to your app and refresh the page (Note: this might take a few minutes to take effect after publishing)\\n |
|
\\n\"\n },\n {\n \"id\": 7545,\n \"title\": \"Anchored Links\",\n \"content\": \"How to Create an Anchored Link\\nAnchored links allow users to quickly access the information that is most relevant to them on the page.\\nAnchored links function similarly to hyperlinks however instead of directing a user to a new page entirely, anchored links direct users to different sections within the same page. They can be used across all livepro knowledge objects.\\n**Tip**: It is easiest to create your anchored links once you have finished authoring all your content into the page.\\nPart 1 - Creating the Anchor\\n1. Highlight the content that you want your link to direct the user to \\n \\n2. Click on the 'Anchor' button on the editor (Insert > Anchor)\\n3. Enter an 'Anchor ID' of your choice into the pop-up box and click 'OK'. This ID acts as your reference when linking up content later in the process\\n4. You will see a little anchor symbol appear next to your selected text. \\nPart 2 - Linking Content to Anchor\\n1. Highlight the section of text that you want to create a link of out (Once complete, the user will click on this text and the link will take them to the content in step 1)\\n2. Click on the 'Insert/Edit Link' button on the editor\\n3. Select the 'Anchors' drop-down menu and click on the Anchor ID that you created in part 1\\n4. Select **None** from the Target drop-down menu\\n5. Click 'OK'\\n6. Save your knowledge object and test that the link works\\nExample\\nThe screen capture below takes you through a live example of how to create an anchored link. In this example, we have used anchors to help users navigate this glossary of tea types more easily.\\n
\\n\"\n },\n {\n \"id\": 6490,\n \"title\": \"Adding or Changing a Homepage in livepro\",\n \"content\": \"A homepage can be created so it can be used as the landing page once a user logs into livepro. You can create the homepage from scratch or use an existing knowledge object. Note: This means users will no longer default to the announcements page upon login.\\nThere are two ways to set a homepage:\\n1. For all users\\n2. For individual roles (great for different teams and departments)\\n
|  | Since a homepage is just a regular knowledge object, it still respects permissions. This means if the page isn't published or in a category the user has access to, the homepage won't appear for the user. |
\\nSetting a homepage for all users\\nIn order to set the homepage, the knowledge object must have a [permalink](/view/6512 \\\"What is a Permalink\\\") of https://\\\\*\\\\*\\\\*.livepro.com.au/goto/home\\nwhere \\\\*\\\\*\\\\* is the name of your company's livepro site.\\n1. Create or edit an existing knowledge object to include the content that is required to be shown on the home page\\n2. In the knowledge object header, change the permalink to say '**home**'\\n3. Save the knowledge object\\n4. Log out of livepro and log back in to see that the knowledge object is now displaying for all users.\\n\\nDifferent Role, Different Homepage\\nAll users will have the same homepage if it is set using the permalink option above, however the option to have different homepages can be setup for different roles.\\n**Note:** Only users who have administrator access in your livepro site will be able to assign different homepages to different roles.\\nTo update the homepage for each role:\\n1. Obtain the permalink of the knowledge object you would like to use as the homepage\\n2. Once you have the permalink, click the livepro icon located on the top right of the livepro website\\n3. Click the **Roles** icon\\n4. Select the Role which you would like to assign a homepage and select '**edit**'\\n5. Enter the last part of the permalink into the **HOME PERMALINK** field. e.g. If permalink is 'https://learn.livepro.com.au/goto/test-homepage, then enter \\\"test-homepage\\\" into the **LOGO PERMALINK** field.\\n6. Click **Save**\\n7. When the user with the assigned role logs into livepro, the homepage will now appear.\\n\\n**Note:** Should the user have multiple roles assigned to them with different homepages, their default view will be the announcements window.\\nAlternatively, users with multiple roles may choose a specific homepage based on their available roles.\\nTo update the default homepage for the role:\\n1. Hover or click the **User Name** on the upper right screen.\\n2. Click '**settings**'\\n3. Select the '**Homepage selection**' dropdown. Note: Only a list of roles with *available* homepage will appear in the dropdown option.\\n4. Click **Done.**\\n5. Click on the livepro logo on the upper left side of the screen to refresh and view the default homepage you selected.\\n
\\n\"\n },\n {\n \"id\": \"8946\",\n \"title\": \"1.2 - Knowledge Types\",\n \"content\": \"Knowledge Types\\nLearning Outcomes\\nBy the end of this module, you should:\\n- have a basic understanding of the different types of knowledge in livepro\\nInstructions\\n\\nHelp Articles, Tips & Tricks\\n[What is a knowledge object?](/view/7955 \\\"What is a Knowledge Object?\\\") \\n[Knowledge Objects - What to Include](/view/7956 \\\"Knowledge Objects - What to Include\\\")\\nNext Steps\\nNow that you know how to setup different types of knowledge, [click here to get started with a document note.](/view/8947 \\\"3. Header Fields & Document Notes \\\")
\\n\"\n }\n ],\n \"count\": 16,\n \"facets\": {\n \"Status\": [\n {\n \"text\": \"Pending\",\n \"documents\": 2,\n \"active\": 0,\n \"link\": \"Pending(2)\",\n \"field\": \"future_workflow_status_description\",\n \"parameters\": {\n \"query\": \"test\",\n \"outputformat\": \"json\",\n \"search_mode\": \"neural\",\n \"source\": \"genai\",\n \"options\": \"content_only_markdown\",\n \"future_workflow_status_description\": \"Pending\"\n }\n },\n {\n \"text\": \"Published\",\n \"documents\": 91,\n \"active\": 0,\n \"link\": \"Published(91)\",\n \"field\": \"future_workflow_status_description\",\n \"parameters\": {\n \"query\": \"test\",\n \"outputformat\": \"json\",\n \"search_mode\": \"neural\",\n \"source\": \"genai\",\n \"options\": \"content_only_markdown\",\n \"future_workflow_status_description\": \"Published\"\n }\n }\n ],\n \"Knowledge Type\": [\n {\n \"text\": \"Document Note\",\n \"documents\": 82,\n \"active\": 0,\n \"link\": \"Document Note(82)\",\n \"field\": \"type_description\",\n \"parameters\": {\n \"query\": \"test\",\n \"outputformat\": \"json\",\n \"search_mode\": \"neural\",\n \"source\": \"genai\",\n \"options\": \"content_only_markdown\",\n \"type_description\": \"Document Note\"\n }\n },\n {\n \"text\": \"Hub\",\n \"documents\": 4,\n \"active\": 0,\n \"link\": \"Hub(4)\",\n \"field\": \"type_description\",\n \"parameters\": {\n \"query\": \"test\",\n \"outputformat\": \"json\",\n \"search_mode\": \"neural\",\n \"source\": \"genai\",\n \"options\": \"content_only_markdown\",\n \"type_description\": \"Hub\"\n }\n },\n {\n \"text\": \"Rocket\",\n \"documents\": 2,\n \"active\": 0,\n \"link\": \"Rocket(2)\",\n \"field\": \"type_description\",\n \"parameters\": {\n \"query\": \"test\",\n \"outputformat\": \"json\",\n \"search_mode\": \"neural\",\n \"source\": \"genai\",\n \"options\": \"content_only_markdown\",\n \"type_description\": \"Rocket\"\n }\n },\n {\n \"text\": \"Work Instruction\",\n \"documents\": 5,\n \"active\": 0,\n \"link\": \"Work Instruction(5)\",\n \"field\": \"type_description\",\n \"parameters\": {\n \"query\": \"test\",\n \"outputformat\": \"json\",\n \"search_mode\": \"neural\",\n \"source\": \"genai\",\n \"options\": \"content_only_markdown\",\n \"type_description\": \"Work Instruction\"\n }\n }\n ],\n \"Average Score\": [\n {\n \"text\": 5,\n \"documents\": 1,\n \"active\": 0,\n \"link\": \"5(1)\",\n \"field\": \"average_score\",\n \"parameters\": {\n \"query\": \"test\",\n \"outputformat\": \"json\",\n \"search_mode\": \"neural\",\n \"source\": \"genai\",\n \"options\": \"content_only_markdown\",\n \"average_score\": 5\n }\n }\n ],\n \"Expired\": [\n {\n \"text\": 0,\n \"documents\": 93,\n \"active\": 0,\n \"link\": \"0(93)\",\n \"field\": \"is_expired_b\",\n \"parameters\": {\n \"query\": \"test\",\n \"outputformat\": \"json\",\n \"search_mode\": \"neural\",\n \"source\": \"genai\",\n \"options\": \"content_only_markdown\",\n \"is_expired_b\": 0\n }\n }\n ],\n \"Parent category\": [\n {\n \"text\": \"Help\",\n \"documents\": 93,\n \"active\": 0,\n \"link\": \"Help(93)\",\n \"field\": \"hierarchy_toplevel\",\n \"parameters\": {\n \"query\": \"test\",\n \"outputformat\": \"json\",\n \"search_mode\": \"neural\",\n \"source\": \"genai\",\n \"options\": \"content_only_markdown\",\n \"hierarchy_toplevel\": \"Help\"\n }\n }\n ]\n },\n \"total\": 16,\n \"parameters\": {\n \"query\": \"test\",\n \"outputformat\": \"json\",\n \"search_mode\": \"neural\",\n \"source\": \"genai\",\n \"options\": \"content_only_markdown\",\n \"search_mode_executed\": \"hybrid\"\n },\n \"facets_returned\": {\n \"type_description\": {\n \"Document Note\": 82,\n \"Hub\": 4,\n \"Rocket\": 2,\n \"Work Instruction\": 5\n },\n \"average_score\": {\n \"5\": 1\n },\n \"is_expired_b\": {\n \"No\": 93\n },\n \"hierarchy_toplevel\": {\n \"Help\": 93\n },\n \"future_workflow_status_description\": {\n \"Pending\": 2,\n \"Published\": 91\n }\n },\n \"facets_translation\": {\n \"type_description\": \"Knowledge Type\",\n \"average_score\": \"Average Score\",\n \"is_expired_b\": \"Expired\",\n \"hierarchy_toplevel\": \"Parent category\",\n \"future_workflow_status_description\": \"Status\"\n },\n \"scores\": [\n {\n \"knowledge_object_id\": 6377,\n \"score\": \"100\",\n \"solr_score\": 0.8165232\n },\n {\n \"knowledge_object_id\": 9296,\n \"score\": \"65\",\n \"solr_score\": 0.5277955\n },\n {\n \"knowledge_object_id\": 9067,\n \"score\": \"60\",\n \"solr_score\": 0.48762405\n },\n {\n \"knowledge_object_id\": 9797,\n \"score\": \"59\",\n \"solr_score\": 0.48472732\n },\n {\n \"knowledge_object_id\": 9796,\n \"score\": \"49\",\n \"solr_score\": 0.40298685\n },\n {\n \"knowledge_object_id\": 9609,\n \"score\": \"48\",\n \"solr_score\": 0.3906204\n },\n {\n \"knowledge_object_id\": 9339,\n \"score\": \"48\",\n \"solr_score\": 0.38855487\n },\n {\n \"knowledge_object_id\": 9313,\n \"score\": \"47\",\n \"solr_score\": 0.3815366\n },\n {\n \"knowledge_object_id\": 4738,\n \"score\": \"46\",\n \"solr_score\": 0.37393656\n },\n {\n \"knowledge_object_id\": 9417,\n \"score\": \"46\",\n \"solr_score\": 0.3734798\n },\n {\n \"knowledge_object_id\": 4742,\n \"score\": \"45\",\n \"solr_score\": 0.36815646\n },\n {\n \"knowledge_object_id\": 9072,\n \"score\": \"44\",\n \"solr_score\": 0.3593726\n },\n {\n \"knowledge_object_id\": 9454,\n \"score\": \"36\",\n \"solr_score\": 0.2978802\n },\n {\n \"knowledge_object_id\": 7545,\n \"score\": \"30\",\n \"solr_score\": 0.24650095\n },\n {\n \"knowledge_object_id\": 6490,\n \"score\": \"29\",\n \"solr_score\": 0.23378041\n },\n {\n \"knowledge_object_id\": 8946,\n \"score\": \"25\",\n \"solr_score\": 0.20293415\n }\n ],\n \"spellcheck\": [],\n \"sort_fields\": [\n {\n \"label\": \"score\",\n \"order\": \"score\"\n },\n {\n \"label\": \"Title\",\n \"order\": \"title_sort\"\n },\n {\n \"label\": \"Created date\",\n \"order\": \"create_date\"\n }\n ]\n}"}],"_postman_id":"33ee5142-6ff7-4886-bcff-dfd15fb007df"},{"name":"Read knowledge object","id":"6ffa8ff0-1abb-4b0a-ba57-1bf2d1986712","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://help.livepro.com.au/livepro-api/read?id=4196&name=&hidetitle=false&outputformat=json&call_function=openLiveproRecord&version_id","description":"Gets a knowledge object to display to the user
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}},"urlObject":{"protocol":"https","path":["livepro-api","read"],"host":["help","livepro","com","au"],"query":[{"description":{"content":"The ID of the knowledge object to load(see: name)
\n","type":"text/plain"},"key":"id","value":"4196"},{"description":{"content":"The name of the knowledge object to load(see: id)
\n","type":"text/plain"},"key":"name","value":""},{"description":{"content":"Boolean that will hide the title when output format is html
\n","type":"text/plain"},"key":"hidetitle","value":"false"},{"description":{"content":"The format in which results should be returned, can be json/html
\n","type":"text/plain"},"key":"outputformat","value":"json"},{"description":{"content":"Callback function to call when a livepro link is clicked. This function should take an id as a parameter.
\n","type":"text/plain"},"key":"call_function","value":"openLiveproRecord"},{"description":{"content":"The ID of the knowledge object version to load (optional)
\n","type":"text/plain"},"key":"version_id","value":null}],"variable":[]}},"response":[{"id":"03c7d2a4-743f-4561-bc0b-c7a1c74b9c64","name":"Read knowledge object","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://help.livepro.com.au/livepro-api/read?id=4196&hidetitle=false&outputformat=json&call_function=openLiveproRecord&apikey=8850fdc718e5da1e86ed4a8fe23f0c73","protocol":"https","host":["help","livepro","com","au"],"path":["livepro-api","read"],"query":[{"key":"id","value":"4196","description":"Knowledge object 3257"},{"key":"hidetitle","value":"false"},{"key":"outputformat","value":"json","description":"The format in which results should be returned, can be json/html"},{"key":"call_function","value":"openLiveproRecord","description":"Callback function"},{"key":"apikey","value":"8850fdc718e5da1e86ed4a8fe23f0c73","type":"text"}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":null,"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"record\": {\n \"id\": \"4196\",\n \"version_id\": \"29705\",\n \"type\": \"documentnote\",\n \"title\": \"How to Create a Document Note\",\n \"permalink\": \"how-to-create-a-document-note\",\n \"content\": \"What is a document note?
\\nA document note is your base level of information in livepro. It should contain answers, policy information, guidelines, FAQs, product information etc.
\\nIf you're not sure which knowledge to use, have a look here.
\\nHow to create a document note
\\n\\n\\n\\n| 1 | \\n\\n Click Create (![\\\"\\\"](\\\"https://help.livepro.com.au/livepro-api/read?id=4309&context=image\\\") ) on the top right navigation bar. \\n | \\n
\\n\\n| 2 | \\n\\n In the Create Knowledge pop-up box select: \\n\\n- Type: Document Note
\\n- Workflow: (Default is the most common)
\\n \\n | \\n
\\n\\n| 3 | \\n\\n Click Continue \\n | \\n
\\n\\n| 4 | \\n\\n Populate the Knowledge Object Header Fields with all relevant information \\n | \\n
\\n\\n| 5 | \\n\\n Use the WYSIWYG editor to create your content. Hint: insert a template to ensure consistency amongst your site! \\n | \\n
\\n\\n| 6 | \\n\\n In the Categories tab, select the document note category, this is the location you want your document note stored within livepro.
Click and drag your selection from the Available Categories column to the Selected Categories column. \\n\\n\\n\\n![](\\\"https://help.livepro.com.au/livepro-api/read?id=855&context=image\\\") | \\nTip: More than one category can be selected. To remove incorrect categories from the Selected Categories column click to highlight the incorrect option and select the rubbish bin icon. | \\n \\n\\n \\n | \\n
\\n\\n| 7 | \\n\\n In the Options tab, select the options for your Document Note.
When the options are ticked: \\n\\n- Acknowledgement: Allows the system to see if the user has read the Knowledge Object (only applies to Announcements)
\\n- Favourite: Allows the user to add the Document Note to their Favourites list.
\\n- Feedback: Allows the user to provide feedback on the Document Note.
\\n- Rating: Allows the user to rate the Document Note.
\\n- Search: Allows users to find the Document Note through search.
\\n \\n\\n\\n\\n | \\nTip: Did you know you can make the document note invisible in the category list? see How to Hide a Knowledge Object for more information. | \\n \\n\\n \\n | \\n
\\n\\n| 8 | \\n\\n Click Save at the top of the document note
In the New Version Prefix pop-up box, you can enter your comments, this is optional. These comments are visible to other authors in the history view and can provide information on why and what changes were made.
Click Continue. \\n | \\n
\\n\\n![](\\\"https://help.livepro.com.au/livepro-api/read?id=2097&context=image\\\") | \\n\\n Content is now published! \\n | \\n
\\n\\n![](\\\"https://help.livepro.com.au/livepro-api/read?id=5280&context=image\\\") | \\n
\\n\\n
\\n
\\n\",\n \"related_links\": [\n {\n \"title\": \"Features: Authoring in the WYSIWYG Editor\",\n \"ordering\": \"0\",\n \"reversed\": false,\n \"to_record_id\": \"1927\",\n \"from_record_id\": \"4196\"\n },\n {\n \"title\": \"How to add Internal links\",\n \"ordering\": \"2\",\n \"reversed\": false,\n \"to_record_id\": \"4230\",\n \"from_record_id\": \"4196\"\n },\n {\n \"title\": \"How to add External links\",\n \"ordering\": \"4\",\n \"reversed\": false,\n \"to_record_id\": \"4218\",\n \"from_record_id\": \"4196\"\n },\n {\n \"title\": \"How to add Related links\",\n \"ordering\": \"6\",\n \"reversed\": false,\n \"to_record_id\": \"4226\",\n \"from_record_id\": \"4196\"\n },\n {\n \"title\": \"Options Tab\",\n \"ordering\": \"7\",\n \"reversed\": false,\n \"to_record_id\": \"4193\",\n \"from_record_id\": \"4196\"\n }\n ],\n \"feedback\": true\n }\n}"}],"_postman_id":"6ffa8ff0-1abb-4b0a-ba57-1bf2d1986712"}],"id":"5e0c7b3b-e556-4e0b-8c65-8cac46e36843","_postman_id":"5e0c7b3b-e556-4e0b-8c65-8cac46e36843","description":"","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}}},{"name":"Categories","item":[{"name":"Read category","id":"fb8c8211-b8e6-4b9b-b741-b21649daece3","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://help.livepro.com.au/api/categorylist?id=64","description":"Read category will fetch the knowledge objects inside of a category along with any subcategories that exist in the category.
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}},"urlObject":{"protocol":"https","path":["api","categorylist"],"host":["help","livepro","com","au"],"query":[{"description":{"content":"The ID of the category
\n","type":"text/plain"},"key":"id","value":"64"}],"variable":[]}},"response":[{"id":"d798efbe-fc8f-459d-9a87-1341a1de6869","name":"Read category","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://help.livepro.com.au/api/categorylist?id=64&apikey=8850fdc718e5da1e86ed4a8fe23f0c73","protocol":"https","host":["help","livepro","com","au"],"path":["api","categorylist"],"query":[{"key":"id","value":"64"},{"key":"apikey","value":"8850fdc718e5da1e86ed4a8fe23f0c73"}]}},"_postman_previewlanguage":"json","header":null,"cookie":[],"responseTime":null,"body":"{\n \"category\": {\n \"id\": \"64\",\n \"description\": \"Features\",\n \"summary\": \"Understand the features livepro has to offer\",\n \"knowledge_objects\": [\n {\n \"id\": \"8968\",\n \"version_id\": \"30464\",\n \"title\": \"Advanced Search\",\n \"summary\": \"How to use the Advanced Search feature in livepro\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8968&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/advanced-search\"\n },\n {\n \"id\": \"1917\",\n \"version_id\": \"29760\",\n \"title\": \"Announcements - Features\",\n \"summary\": \"The features of an announcement\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=1917&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/features-announcements\"\n },\n {\n \"id\": \"8033\",\n \"version_id\": \"29681\",\n \"title\": \"Deleting Knowledge Objects in livepro\",\n \"summary\": \"Removing knowledge stored in livepro\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8033&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/deleting-knowledge-objects-in-livepro\"\n },\n {\n \"id\": \"3257\",\n \"version_id\": \"29563\",\n \"title\": \"Document Notes - Features\",\n \"summary\": \"Features of a document note\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=3257&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/document-notes-features\"\n },\n {\n \"id\": \"8720\",\n \"version_id\": \"30786\",\n \"title\": \"Edit your own profile as a user\",\n \"summary\": \"Instructions on how users can edit their own profiles\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8720&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/edit-your-own-profile-as-a-user\"\n },\n {\n \"id\": \"4195\",\n \"version_id\": \"29714\",\n \"title\": \"Features of the WYSIWYG Editor\",\n \"summary\": \"Features of the WYSIWYG editor\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=4195&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/wysiwyg\"\n },\n {\n \"id\": \"8634\",\n \"version_id\": \"30705\",\n \"title\": \"Help Features\",\n \"summary\": \"What does the help button do?\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8634&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/help-features\"\n },\n {\n \"id\": \"4375\",\n \"version_id\": \"29796\",\n \"title\": \"Information about Announcements\",\n \"summary\": \"Benefits and Features of Announcements\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=4375&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/information-about-announcements\"\n },\n {\n \"id\": \"4383\",\n \"version_id\": \"30462\",\n \"title\": \"Knowledge Object Header Fields\",\n \"summary\": \"Explanation of the standard header fields in all knowledge objects\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=4383&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/knowledge-object-header-fields\"\n },\n {\n \"id\": \"7956\",\n \"version_id\": \"28062\",\n \"title\": \"Knowledge Objects - What to Include\",\n \"summary\": \"What should you include in your Knowledge Objects?\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=7956&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/knowledge-objects-what-to-include\"\n },\n {\n \"id\": \"4738\",\n \"version_id\": \"30784\",\n \"title\": \"Listing Menu\",\n \"summary\": \"The listing menu allows you to search all information stored in livepro\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=4738&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/what-is-a-listing\"\n },\n {\n \"id\": \"8034\",\n \"version_id\": \"26111\",\n \"title\": \"livepro Communities\",\n \"summary\": \"What and where is livepro Communities\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8034&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/livepro-communities\"\n },\n {\n \"id\": \"8117\",\n \"version_id\": \"29835\",\n \"title\": \"livepro Licenses\",\n \"summary\": \"This table illustrates the licensing options available from livepro\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8117&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/livepro-licenses\"\n },\n {\n \"id\": \"9084\",\n \"version_id\": \"30868\",\n \"title\": \"Navigation Bar\",\n \"summary\": \"What is the Navigation Bar and how do I use it?\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=9084&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/navigation-bar\"\n },\n {\n \"id\": \"8039\",\n \"version_id\": \"30474\",\n \"title\": \"Printing Knowledge Objects from livepro\",\n \"summary\": \"Can I print livepro content?\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8039&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/printing-knowledge-objects-from-livepro\"\n },\n {\n \"id\": \"8887\",\n \"version_id\": \"29750\",\n \"title\": \"Problems, Issues & Support\",\n \"summary\": \"What to do when you need further support or assistance\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8887&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/problems-issues-amp-support\"\n },\n {\n \"id\": \"8620\",\n \"version_id\": \"30652\",\n \"title\": \"Resources\",\n \"summary\": \"What are Resources and how to use them?\",\n \"type\": \"hub\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8620&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/resources1\"\n },\n {\n \"id\": \"8711\",\n \"version_id\": \"30648\",\n \"title\": \"Rocket Example\",\n \"summary\": \"Example of the livepro Rocket\",\n \"type\": \"wizard2\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8711&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/rocket-example\"\n },\n {\n \"id\": \"1965\",\n \"version_id\": \"30939\",\n \"title\": \"Search\",\n \"summary\": \"Learn more about the search function and how to optimise search results \",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=1965&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/search\"\n },\n {\n \"id\": \"9067\",\n \"version_id\": \"30681\",\n \"title\": \"Spell Check\",\n \"summary\": \"Is there a spell checker in livepro?\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=9067&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/spell-check\"\n },\n {\n \"id\": \"5329\",\n \"version_id\": \"30951\",\n \"title\": \"Version Control\",\n \"summary\": \"Explains how version control works in livepro\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=5329&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/version-control\"\n },\n {\n \"id\": \"8672\",\n \"version_id\": \"30463\",\n \"title\": \"Viewing livepro content on a mobile device\",\n \"summary\": \"Instructions on how to view livepro content on a mobile device\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=8672&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/viewing-livepro-content-on-a-mobile-device\"\n },\n {\n \"id\": \"5324\",\n \"version_id\": \"29709\",\n \"title\": \"What are Favourites?\",\n \"summary\": \"Explains what favourites are used for in livepro\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=5324&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/what-are-favourites\"\n },\n {\n \"id\": \"7955\",\n \"version_id\": \"30475\",\n \"title\": \"What is a Knowledge Object?\",\n \"summary\": \"What are the different types of knowledge objects in livepro and which should I use?\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=7955&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/what-is-a-knowledge-object\"\n },\n {\n \"id\": \"3814\",\n \"version_id\": \"30221\",\n \"title\": \"What is a Quiz?\",\n \"summary\": \"Provides information on what a quiz is. \",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=3814&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/what-is-a-quiz\"\n },\n {\n \"id\": \"4742\",\n \"version_id\": \"30491\",\n \"title\": \"What is Feedback?\",\n \"summary\": \"Shows how to add feedback in livepro\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=4742&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/what-is-feedback\"\n },\n {\n \"id\": \"1927\",\n \"version_id\": \"29964\",\n \"title\": \"What is the WYSIWYG Editor?\",\n \"summary\": \"Introduction to the WYSIWYG editor \",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=1927&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/wysiwyg-editor\"\n },\n {\n \"id\": \"4732\",\n \"version_id\": \"30224\",\n \"title\": \"What is Workflow?\",\n \"summary\": \"Definition of workflow and how it works in livepro\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/read?outputformat=json&id=4732&apikey=8850fdc718e5da1e86ed4a8fe23f0c73\",\n \"permalink\": \"https://help.livepro.com.au/goto/what-is-workflow\"\n }\n ]\n },\n \"sub_categories\": []\n}"}],"_postman_id":"fb8c8211-b8e6-4b9b-b741-b21649daece3"},{"name":"Get category list","id":"32f1a275-008d-4da7-8d7a-1613fee3b77f","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://help.livepro.com.au/api/hierarchies/read?context=tree&id=36","description":"Get category list will show you a list of categories. This is especially useful when building menus or displaying categories across a page.
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}},"urlObject":{"protocol":"https","path":["api","hierarchies","read"],"host":["help","livepro","com","au"],"query":[{"description":{"content":"The context defines the way in which livepro will return the list of categories, should be set to tree
\n","type":"text/plain"},"key":"context","value":"tree"},{"description":{"content":"The ID of the category you want to list.
\n","type":"text/plain"},"key":"id","value":"36"}],"variable":[]}},"response":[{"id":"c1b3b71c-4320-49e5-a051-7bbcde36ae60","name":"Get category list","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://help.livepro.com.au/api/hierarchies/read?apikey=8850fdc718e5da1e86ed4a8fe23f0c73&context=tree&id=36","protocol":"https","host":["help","livepro","com","au"],"path":["api","hierarchies","read"],"query":[{"key":"apikey","value":"8850fdc718e5da1e86ed4a8fe23f0c73","description":"Your api key"},{"key":"context","value":"tree","description":"Get the list in the tree context"},{"key":"id","value":"36","description":"Show category 36"}]}},"_postman_previewlanguage":null,"header":null,"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"nodes\": [\n {\n \"id\": \"64\",\n \"description\": \"Features\",\n \"user_modifiable\": \"1\",\n \"parent_hierarchy_id\": \"36\",\n \"node_type\": \"hierarchy-content\",\n \"ordering\": \"0\",\n \"hierarchy_type_id\": null,\n \"summary\": \"Understand the features livepro has to offer\",\n \"icon_name\": \"flow-chartpng1\",\n \"node_id\": \"36-64\",\n \"iconCls\": \"hierarchy-content\",\n \"catkocount\": 44,\n \"leaf\": true\n },\n {\n \"id\": \"168\",\n \"description\": \"Creating Knowledge\",\n \"user_modifiable\": \"1\",\n \"parent_hierarchy_id\": \"36\",\n \"node_type\": \"hierarchy-content\",\n \"ordering\": \"1\",\n \"hierarchy_type_id\": null,\n \"summary\": \"Get help on authoring knowledge in livepro\",\n \"icon_name\": \"list-viewpng1\",\n \"node_id\": \"36-168\",\n \"iconCls\": \"hierarchy-content\",\n \"catkocount\": 82,\n \"leaf\": true\n },\n {\n \"id\": \"166\",\n \"description\": \"Reports\",\n \"user_modifiable\": \"1\",\n \"parent_hierarchy_id\": \"36\",\n \"node_type\": \"hierarchy-content\",\n \"ordering\": \"2\",\n \"hierarchy_type_id\": null,\n \"summary\": \"Understand the suite of reports\",\n \"icon_name\": \"taskpng1\",\n \"node_id\": \"36-166\",\n \"iconCls\": \"hierarchy-content\",\n \"catkocount\": 19,\n \"leaf\": true\n },\n {\n \"id\": \"65\",\n \"description\": \"livepro Configuration\",\n \"user_modifiable\": \"1\",\n \"parent_hierarchy_id\": \"36\",\n \"node_type\": \"hierarchy-content\",\n \"ordering\": \"3\",\n \"hierarchy_type_id\": null,\n \"summary\": \"Setting up livepro to suit your needs\",\n \"icon_name\": \"settingspng4\",\n \"node_id\": \"36-65\",\n \"iconCls\": \"hierarchy-content\",\n \"catkocount\": 28,\n \"leaf\": true\n },\n {\n \"id\": \"201\",\n \"description\": \"Training\",\n \"user_modifiable\": \"1\",\n \"parent_hierarchy_id\": \"36\",\n \"node_type\": \"hierarchy-content\",\n \"ordering\": \"4\",\n \"hierarchy_type_id\": null,\n \"summary\": \"First time user? Get some online training!\",\n \"icon_name\": \"document-2png1\",\n \"node_id\": \"36-201\",\n \"iconCls\": \"hierarchy-content\",\n \"catkocount\": 2,\n \"nodes\": [\n {\n \"id\": \"209\",\n \"description\": \"Getting Started\",\n \"user_modifiable\": \"1\",\n \"parent_hierarchy_id\": \"201\",\n \"node_type\": \"hierarchy-content\",\n \"ordering\": \"0\",\n \"hierarchy_type_id\": null,\n \"summary\": \"\",\n \"icon_name\": \"\",\n \"node_id\": \"36-201-209\",\n \"iconCls\": \"hierarchy-content\",\n \"catkocount\": 4,\n \"leaf\": true\n },\n {\n \"id\": \"210\",\n \"description\": \"Editor Functions\",\n \"user_modifiable\": \"1\",\n \"parent_hierarchy_id\": \"201\",\n \"node_type\": \"hierarchy-content\",\n \"ordering\": \"1\",\n \"hierarchy_type_id\": null,\n \"summary\": \"\",\n \"icon_name\": \"\",\n \"node_id\": \"36-201-210\",\n \"iconCls\": \"hierarchy-content\",\n \"catkocount\": 12,\n \"leaf\": true\n },\n {\n \"id\": \"211\",\n \"description\": \"Knowledge Types\",\n \"user_modifiable\": \"1\",\n \"parent_hierarchy_id\": \"201\",\n \"node_type\": \"hierarchy-content\",\n \"ordering\": \"2\",\n \"hierarchy_type_id\": null,\n \"summary\": \"\",\n \"icon_name\": \"\",\n \"node_id\": \"36-201-211\",\n \"iconCls\": \"hierarchy-content\",\n \"catkocount\": 16,\n \"leaf\": true\n },\n {\n \"id\": \"212\",\n \"description\": \"Other\",\n \"user_modifiable\": \"1\",\n \"parent_hierarchy_id\": \"201\",\n \"node_type\": \"hierarchy-content\",\n \"ordering\": \"3\",\n \"hierarchy_type_id\": null,\n \"summary\": \"\",\n \"icon_name\": \"\",\n \"node_id\": \"36-201-212\",\n \"iconCls\": \"hierarchy-content\",\n \"catkocount\": 3,\n \"leaf\": true\n }\n ]\n },\n {\n \"id\": \"213\",\n \"description\": \"Addons & Integrations\",\n \"user_modifiable\": \"1\",\n \"parent_hierarchy_id\": \"36\",\n \"node_type\": \"hierarchy-content\",\n \"ordering\": \"5\",\n \"hierarchy_type_id\": null,\n \"summary\": \"Systems we integrate with and additional addons\",\n \"icon_name\": \"timesheetpng1\",\n \"node_id\": \"36-213\",\n \"iconCls\": \"hierarchy-content\",\n \"catkocount\": 21,\n \"leaf\": true\n }\n ]\n}"}],"_postman_id":"32f1a275-008d-4da7-8d7a-1613fee3b77f"}],"id":"62d36b70-e8af-47af-81fb-811cbd4e802d","_postman_id":"62d36b70-e8af-47af-81fb-811cbd4e802d","description":"","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}}},{"name":"Feedback","item":[{"name":"Feedback","id":"435c2d57-70b8-4069-b764-46aa4d26230a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/json","type":"text"}],"body":{"mode":"raw","raw":"{\n \"data\": {\n \"responses\": [\n \t{\n \t\"content\": {\n \t\"html\": \"Feedback content\"\n \t},\n \t\"knowledge_object_version_id\": \"7545\",\n \t\"response_type_id\": \"1\"\n \t}\n ]\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://help.livepro.com.au/livepro-api/feedback","description":"This allows you to submit feedback into livepro via the api. It can be done with a knowledge object which will assign the feedback against it or it can be done without and will create general feedback.
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}},"urlObject":{"protocol":"https","path":["livepro-api","feedback"],"host":["help","livepro","com","au"],"query":[{"disabled":true,"key":"source","value":"api"}],"variable":[]}},"response":[{"id":"bc30beda-0d3e-4b05-9708-5ec0b8825162","name":"General feedback","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/json","type":"text"}],"body":{"mode":"raw","raw":"{\n \"data\": {\n \"responses\": [\n {\n \"content\": {\n \"html\": \"General feedback for the whole site\"\n },\n \"response_type_id\": \"1\"\n }\n ]\n }\n}","options":{"raw":{"language":"json"}}},"url":{"raw":"https://{{client_id}}.livepro.com.au/livepro-api/feedback?apikey=abdefgapikey","protocol":"https","host":["{{client_id}}","livepro","com","au"],"path":["livepro-api","feedback"],"query":[{"key":"source","value":"api","disabled":true},{"key":"apikey","value":"abdefgapikey","description":"Your API key"}]}},"_postman_previewlanguage":"json","header":null,"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"responses\": [{\n \"id\": \"4143\",\n \"title\": \"\",\n \"summary\": \"\",\n \"knowledge_object_version_id\": null,\n \"knowledge_object_version_title\": null,\n \"knowledge_object_version_version\": null,\n \"knowledge_object_version_subversion\": null,\n \"knowledge_object_type_code\": null,\n \"knowledge_object_id\": null,\n \"responses\": null,\n \"response_type_id\": \"1\",\n \"response_type_description\": \"Feedback\",\n \"response_status_id\": \"1\",\n \"response_status_description\": \"pending\",\n \"response_status_archived\": \"0\",\n \"response_type_code\": null,\n \"response_parent_id\": null,\n \"action_id\": \"1\",\n \"action_description\": \"Create\",\n \"author_user_id\": \"2\",\n \"author_username\": \"admin\",\n \"author_firstname\": \"livepro\",\n \"author_lastname\": \"Admin\",\n \"author_image_id\": \"1226\",\n \"author_fullname\": \"livepro Admin\",\n \"creator_user_id\": \"2\",\n \"creator_username\": \"admin\",\n \"creator_firstname\": \"livepro\",\n \"creator_lastname\": \"Admin\",\n \"creator_image_id\": \"1226\",\n \"creator_fullname\": \"livepro Admin\",\n \"responsible_user_id\": null,\n \"responsible_username\": null,\n \"responsible_firstname\": null,\n \"responsible_lastname\": null,\n \"responsible_image_id\": null,\n \"responsible_fullname\": null,\n \"content\": {\n \"title\": \"\",\n \"html\": \"General feedback for the whole site\"\n },\n \"create_date\": \"2019-10-04 05:15:13\",\n \"update_date\": \"2019-10-04 05:15:13\",\n \"user_associations\": [],\n \"is_user_favorite\": 0,\n \"is_user_responsible\": 0,\n \"errors_response\": []\n }],\n \"sort_fields\": [{\n \"label\": \"Created date\",\n \"order\": \"create_date\",\n \"active\": \"1\",\n \"direction\": \"asc\"\n }]\n}"},{"id":"de726a9a-7cdb-4498-a608-615ad35ce284","name":"Feedback for knowledge object","originalRequest":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","value":"application/json","type":"text"}],"body":{"mode":"raw","raw":"{\n \"data\": {\n \"responses\": [\n \t{\n \t\"content\": {\n \t\"html\": \"The pricing listed is last years prices and needs to be updated\"\n \t},\n \t\"knowledge_object_version_id\": \"4359\",\n \t\"response_type_id\": \"1\"\n \t}\n ]\n }\n}","options":{"raw":{"language":"json"}}},"url":{"raw":"https://{{client_id}}.livepro.com.au/livepro-api/feedback?apikey=abdefgapikey","protocol":"https","host":["{{client_id}}","livepro","com","au"],"path":["livepro-api","feedback"],"query":[{"key":"source","value":"api","disabled":true},{"key":"apikey","value":"abdefgapikey","description":"Your API key"}]}},"_postman_previewlanguage":"json","header":null,"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"responses\": [\n {\n \"id\": \"4144\",\n \"title\": \"\",\n \"summary\": \"\",\n \"knowledge_object_version_id\": \"4359\",\n \"knowledge_object_version_title\": \"Camp Grounds Pricing\",\n \"knowledge_object_version_version\": \"1\",\n \"knowledge_object_version_subversion\": \"3\",\n \"knowledge_object_type_code\": \"documentnote\",\n \"knowledge_object_id\": \"1237\",\n \"responses\": [],\n \"response_type_id\": \"1\",\n \"response_type_description\": \"Feedback\",\n \"response_status_id\": \"1\",\n \"response_status_description\": \"pending\",\n \"response_status_archived\": \"0\",\n \"response_type_code\": null,\n \"response_parent_id\": null,\n \"action_id\": \"1\",\n \"action_description\": \"Create\",\n\t \"author_user_id\": \"2\",\n\t \"author_username\": \"admin\",\n\t \"author_firstname\": \"livepro\",\n\t \"author_lastname\": \"Admin\",\n\t \"author_image_id\": \"1226\",\n\t \"author_fullname\": \"livepro Admin\",\n\t \"creator_user_id\": \"2\",\n\t \"creator_username\": \"admin\",\n\t \"creator_firstname\": \"livepro\",\n\t \"creator_lastname\": \"Admin\",\n\t \"creator_image_id\": \"1226\",\n\t \"creator_fullname\": \"livepro Admin\",\n \"responsible_user_id\": null,\n \"responsible_username\": null,\n \"responsible_firstname\": null,\n \"responsible_lastname\": null,\n \"responsible_image_id\": null,\n \"responsible_fullname\": null,\n \"content\": {\n \"title\": \"\",\n \"html\": \"The pricing listed is last years prices and needs to be updated\"\n },\n \"create_date\": \"2019-10-04 05:18:18\",\n \"update_date\": \"2019-10-04 05:18:18\",\n \"user_associations\": [],\n \"is_user_favorite\": 0,\n \"is_user_responsible\": 0,\n \"errors_response\": []\n }\n ],\n \"allowed_actions\": {\n \"4359\": [\n \"create\",\n \"edit\",\n \"editfeedback\",\n \"read\",\n \"markasread\",\n \"markasunread\",\n \"usefeedback\",\n \"rate\"\n ]\n }\n}"}],"_postman_id":"435c2d57-70b8-4069-b764-46aa4d26230a"}],"id":"15a087c7-c6b1-42b0-8643-159268e4a6f4","_postman_id":"15a087c7-c6b1-42b0-8643-159268e4a6f4","description":"","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}}},{"name":"Ingestion","item":[{"name":"Ingest Catalog","id":"2c792160-f90f-4c3f-b53f-ec484f33ee3a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://help.livepro.com.au/livepro-api/catalog?query=*","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}},"urlObject":{"protocol":"https","path":["livepro-api","catalog"],"host":["help","livepro","com","au"],"query":[{"key":"query","value":"*"}],"variable":[]}},"response":[{"id":"1662fc63-11c2-4de9-8080-ec4c895fe421","name":"Ingest Catalog","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://help.livepro.com.au/livepro-api/catalog?query=*&limit=5","protocol":"https","host":["help","livepro","com","au"],"path":["livepro-api","catalog"],"query":[{"key":"query","value":"*"},{"key":"limit","value":"5"}]}},"status":"OK","code":200,"_postman_previewlanguage":null,"header":null,"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"total\": 143,\n \"records\": [\n {\n \"id\": \"4195\",\n \"version_id\": \"38787\",\n \"parent_id\": null,\n \"title\": \"WYSIWYG Editor\",\n \"summary\": \"Features of the WYSIWYG editor\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/ingest?id=4195\",\n \"permalink\": \"https://help.livepro.com.au/goto/wysiwyg\",\n \"version\": \"1.49\",\n \"category\": [\n \"Content > Help > Features\"\n ],\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2025-03-20 00:38:22\",\n \"image_id\": \"\"\n },\n {\n \"id\": \"8641\",\n \"version_id\": \"38965\",\n \"parent_id\": null,\n \"title\": \"Workflows\",\n \"summary\": \"What are Workflows?\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/ingest?id=8641\",\n \"permalink\": \"https://help.livepro.com.au/goto/workflows\",\n \"version\": \"1.19\",\n \"category\": [\n \"Content > Help > livepro Configuration\"\n ],\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2025-05-22 16:18:25\",\n \"image_id\": \"\"\n },\n {\n \"id\": \"8638\",\n \"version_id\": \"38962\",\n \"parent_id\": null,\n \"title\": \"Workflow Statuses\",\n \"summary\": \"What are Workflow Statuses and how do I create one?\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/ingest?id=8638\",\n \"permalink\": \"https://help.livepro.com.au/goto/workflow-statuses\",\n \"version\": \"1.28\",\n \"category\": [\n \"Content > Help > livepro Configuration\"\n ],\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2025-05-22 16:04:14\",\n \"image_id\": \"\"\n },\n {\n \"id\": \"8639\",\n \"version_id\": \"38963\",\n \"parent_id\": null,\n \"title\": \"Workflow Patterns\",\n \"summary\": \"\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/ingest?id=8639\",\n \"permalink\": \"https://help.livepro.com.au/goto/workflow-patterns\",\n \"version\": \"1.21\",\n \"category\": [\n \"Content > Help > livepro Configuration\"\n ],\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2025-05-22 16:08:02\",\n \"image_id\": \"\"\n },\n {\n \"id\": \"4732\",\n \"version_id\": \"36991\",\n \"parent_id\": null,\n \"title\": \"Workflow Menu\",\n \"summary\": \"Definition of workflow and how it works in livepro\",\n \"type\": \"documentnote\",\n \"url\": \"https://help.livepro.com.au/livepro-api/ingest?id=4732\",\n \"permalink\": \"https://help.livepro.com.au/goto/what-is-workflow\",\n \"version\": \"1.48\",\n \"category\": [\n \"Content > Help > Features\"\n ],\n \"feedback\": true,\n \"status\": \"Published\",\n \"last_updated\": \"2024-11-21 03:56:29\",\n \"image_id\": \"\"\n }\n ],\n \"count\": 5\n}"}],"_postman_id":"2c792160-f90f-4c3f-b53f-ec484f33ee3a"},{"name":"Ingest Read","id":"264231a2-1f6d-4b82-9b2a-6a2f800d6e88","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://help.livepro.com.au/livepro-api/ingest?id=4195&formatter=markdown","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}},"urlObject":{"protocol":"https","path":["livepro-api","ingest"],"host":["help","livepro","com","au"],"query":[{"description":{"content":"The ID of the knowledge object to read
\n","type":"text/plain"},"key":"id","value":"4195"},{"description":{"content":"Optional, set as markdown for markdown format or leave blank for HTML formatted document
\n","type":"text/plain"},"key":"formatter","value":"markdown"}],"variable":[]}},"response":[{"id":"975310ed-621d-470d-a2ab-aa147cf5df81","name":"Ingest Read","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://help.livepro.com.au/livepro-api/ingest?id=4195","protocol":"https","host":["help","livepro","com","au"],"path":["livepro-api","ingest"],"query":[{"key":"id","value":"4195"}]}},"status":"OK","code":200,"_postman_previewlanguage":null,"header":null,"cookie":[],"responseTime":null,"body":"\n\n\n\n \n WYSIWYG Editor\n\n\n\n\n \n WYSIWYG Editor
\n #4195 Version: 1.49 last updated on 2025-03-20 00:38:22
\n wysiwyg editor source code wysiw thumbnail list checklist bullet numbered wysisyg wisyg\n wysijig tiny mce tinymce aioptions ai options
\n Help
\n \n\n \n The WYSIWYG Editor
\n The WYSIWYG editor in livepro is a great tool to help create and update content, ensuring it is well\n presented. The above toolbar is what you will see when creating new content.
\n ![](\"https://help.livepro.com.au/livepro-api/read?id=9827&context=image\")
\n \n \n \n | WYSIWYG Menu Option | \n What does it do? | \n
\n \n | \n 1. Edit \n | \n \n \n - Undo and Redo - This allows you to undo and redo any changes you make in the editor
\n - Cut/Copy/Paste - Highlight any content and you can either cut or copy it in the editor.\n Use Ctrl + V on your keyboard to paste the cut/copied content.
\n - Paste as Text - This allows text to be pasted into the editor without formatting, such\n as font and colour. You can also use the Ctrl+Shift+V keyboard shortcut.
\n - Select all - Highlights all content in the editor for bulk copy/cut/paste.
\n - Find and replace - Bulk replace all occurrences of a word with another
\n \n | \n
\n \n | \n 2. View \n | \n \n \n - Source Code - View the HTML code of a document. This can be used for creating templates and making advanced changes to knowledge objects
\n - Show blocks - Places a dotted line around paragraphs images and tables. The dotted\n outline will only display in the editor.
\n - Preview - See how the knowledge object will look when viewed by users.
\n \n | \n
\n \n | \n 3. Insert \n | \n \n \n - Media - Embed media from external sites.
\n - Special Character - Insert accented letters and symbols.
\n - Horizontal Line - Inserts a horizontal line at the current cursor position.
\n - Anchors - This\n allows you to jump to the required section of information should you need to scroll\n through the page.
\n - Date/time - Insert current date and time. Note: This will not automatically update.
\n \n | \n
\n \n | \n 4. Format \n | \n \n \n - Strikethrough - Draws a horizontal line across highlighted text. This is an example
\n - Superscript/Subscript - For creating text that appears above or below the normal line of\n text.
\n - Code - Changes the highlighted text to use the <code></code> tag. Useful\n when HTML code needs to be displayed in knowledge objects.
\n - Blocks - Changes the highlighted text to the selected heading/paragraph format.
\n \n | \n
\n \n | \n 5. Tools \n | \n \n \n - Source Code - View the HTML code of a document. This can be used for creating templates and making advanced changes to knowledge objects
\n \n | \n
\n \n | \n 6. Fullscreen \n | \n The knowledge object header will be hidden, allowing more content in WYSIWYG to be displayed on\n the screen. | \n
\n \n | \n 7. Formats \n | \n Format selected text with predefined styles. | \n
\n \n | \n 8. Templates \n | \n To insert a predefined template or snippet of code. | \n
\n \n | \n 9. Insert Image Resource \n | \n Allows you to insert images from livepro or upload a new image. | \n
\n \n | \n 10. Insert Resource \n | \n Allows you to insert links to other\n knowledge objects in livepro. | \n
\n \n | \n 11. Table \n | \n Insert a table at the current cursor position. Sizes between 1x1 and 10x10 can be inserted. | \n
\n \n | \n 12. Insert/Edit and Remove Links \n | \n Allows insertion editing and removal of links. | \n
\n \n | \n 13. Font Size \n | \n Increase or decrease the font size. | \n
\n \n | \n 14. Bold/Italic/Underline \n | \n Add some formatting/emphasis to your text with these tools. | \n
\n \n | \n 15. Text Colour/Background Colour \n | \n To make text stand out you can change the colour of the text or the background behind it. | \n
\n \n | \n 16. Alignment \n | \n Highlight your text and these buttons will align your text to the left/centre/right/full\n justification. | \n
\n \n | \n 17. Numbered List/Bullet List \n | \n Insert a list with several different point options available. | \n
\n \n | \n 18. Decrease indent/Increase indent \n | \n Increase or decrease the indent of text. | \n
\n \n | \n 19. Clear formatting \n | \n Clears all formatting returning the text to black 11pt. Very useful when you want to quickly\n strip all formatting from text. | \n
\n \n | \n 20. Insert Icon \n | \n Select from a variety of icons without the need to upload them as a resource. These Icons can be\n customised by size and colour. | \n
\n \n | \n 21. AI Options \n | \n Allows to refine content and re-write any sentence or paragraph directly in the editor. Simply highlight the text in the page, then click this button.
\n | \n
\n \n
\n \n\n\n\n"},{"id":"be609bd8-e505-4100-8425-a55ee1a892c1","name":"Ingest Read Markdown","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://help.livepro.com.au/livepro-api/ingest?id=4195&formatter=markdown","protocol":"https","host":["help","livepro","com","au"],"path":["livepro-api","ingest"],"query":[{"key":"id","value":"4195"},{"key":"formatter","value":"markdown"}]}},"status":"OK","code":200,"_postman_previewlanguage":null,"header":null,"cookie":[],"responseTime":null,"body":"# WYSIWYG Editor\n\n\\#4195 Version: 1.49 last updated on 2025-03-20 00:38:22\n\n**Keywords:** wysiwyg editor source code wysiw thumbnail list checklist bullet numbered wysisyg wisyg wysijig tiny mce tinymce aioptions ai options\n\n**Categories:** Help\n\n The WYSIWYG Editor\n\nThe WYSIWYG editor in livepro is a great tool to help create and update content, ensuring it is well presented. The above toolbar is what you will see when creating new content.\n\n \n\n WYSIWYG Menu Option What does it do? **1. Edit**\n\n - Undo and Redo - This allows you to undo and redo any changes you make in the editor\n- Cut/Copy/Paste - Highlight any content and you can either cut or copy it in the editor. Use Ctrl + V on your keyboard to paste the cut/copied content.\n- Paste as Text - This allows text to be pasted into the editor without formatting, such as font and colour. You can also use the Ctrl+Shift+V keyboard shortcut.\n- Select all - Highlights all content in the editor for bulk copy/cut/paste.\n- Find and replace - Bulk replace all occurrences of a word with another\n\n **2. View**\n\n - Source Code - View the HTML code of a document. This can be used for creating [templates](https://help.livepro.com.au/livepro-api/read?id=8001&outputformat=plainhtml&apikey=8850fdc718e5da1e86ed4a8fe23f0c73 \"Creating and editing templates\") and making advanced changes to knowledge objects\n- Show blocks - Places a dotted line around paragraphs images and tables. The dotted outline will only display in the editor.\n- Preview - See how the knowledge object will look when viewed by users.\n\n **3. Insert**\n\n - Media - Embed media from external sites.\n- Special Character - Insert accented letters and symbols.\n- Horizontal Line - Inserts a horizontal line at the current cursor position.\n- [Anchors](https://help.livepro.com.au/livepro-api/read?id=7545&outputformat=plainhtml&apikey=8850fdc718e5da1e86ed4a8fe23f0c73 \"Anchored Links\") - This allows you to jump to the required section of information should you need to scroll through the page.\n- Date/time - Insert current date and time. Note: This will not automatically update.\n\n **4. Format**\n\n - Strikethrough - Draws a horizontal line across highlighted text. This is an example\n- Superscript/Subscript - For creating text that appears above or below the normal line of text.\n- Code - Changes the highlighted text to use the <code></code> tag. Useful when HTML code needs to be displayed in knowledge objects.\n- Blocks - Changes the highlighted text to the selected heading/paragraph format.\n\n **5. Tools**\n\n - Source Code - View the HTML code of a document. This can be used for creating [templates](https://help.livepro.com.au/livepro-api/read?id=8001&outputformat=plainhtml&apikey=8850fdc718e5da1e86ed4a8fe23f0c73 \"Creating and editing templates\") and making advanced changes to knowledge objects\n\n **6. Fullscreen**\n\n The knowledge object header will be hidden, allowing more content in WYSIWYG to be displayed on the screen. **7. Formats**\n\n Format selected text with predefined styles. **8. Templates**\n\n To insert a predefined [template](https://help.livepro.com.au/livepro-api/read?id=8001&outputformat=plainhtml&apikey=8850fdc718e5da1e86ed4a8fe23f0c73 \"Creating and editing templates\") or snippet of code. **9. Insert Image Resource**\n\n Allows you to [insert images](https://help.livepro.com.au/livepro-api/read?id=4308&outputformat=plainhtml&apikey=8850fdc718e5da1e86ed4a8fe23f0c73 \"How to add an Image into a Knowledge Object\") from livepro or upload a new image. **10. Insert Resource**\n\n Allows you to insert [ links to other knowledge objects](https://help.livepro.com.au/livepro-api/read?id=4230&outputformat=plainhtml&apikey=8850fdc718e5da1e86ed4a8fe23f0c73 \"How to add Internal Links\") in livepro. **11. Table**\n\n Insert a table at the current cursor position. Sizes between 1x1 and 10x10 can be inserted. **12. Insert/Edit and Remove Links**\n\n Allows insertion editing and removal of links. **13. Font Size**\n\n Increase or decrease the font size. **14. Bold/Italic/Underline**\n\n Add some formatting/emphasis to your text with these tools. **15. Text Colour/Background Colour**\n\n To make text stand out you can change the colour of the text or the background behind it. **16. Alignment**\n\n Highlight your text and these buttons will align your text to the left/centre/right/full justification. **17. Numbered List/Bullet List**\n\n Insert a list with several different point options available. **18. Decrease indent/Increase indent**\n\n Increase or decrease the indent of text. **19. Clear formatting**\n\n Clears all formatting returning the text to black 11pt. Very useful when you want to quickly strip all formatting from text. **20. Insert Icon**\n\n Select from a variety of icons without the need to upload them as a resource. These Icons can be customised by size and colour. **21. AI Options**\n\n Allows to refine content and re-write any sentence or paragraph directly in the editor. Simply highlight the text in the page, then click this button."}],"_postman_id":"264231a2-1f6d-4b82-9b2a-6a2f800d6e88"}],"id":"c2359979-2d11-44a9-b1b0-0decfb420c51","description":"General Expected Workflow
\nTo ensure that the system works as efficiently as possible, without putting unnecessary stress on our systems, the following workflow is expected:
\nInitial run
\n\nRetrieve the list of articles from the \"/catalog\" endpoint
\nIterate through the articles and retrieve articles using the \"/ingest\" endpoint
\nStore a local hash of the id and last_updated fields
\n
\nSubsequent periodic runs
\n\nRetrieve the list of articles from the \"/catalog\" endpoint
\nIterate through the articles and only retrieve articles using the \"/ingest\" endpoint which have a last_updated value greater than that stored in the local hash
\nStore a local hash of the id and last_updated fields
\n
\n","_postman_id":"c2359979-2d11-44a9-b1b0-0decfb420c51","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}}},{"name":"AI","item":[{"name":"Ask AI","id":"7d2b2965-f420-4633-af0a-fc420f7979de","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://help.livepro.com.au/livepro-api/ask-ai?query=how to create a document note","description":"Gets a knowledge object to display to the user
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}},"urlObject":{"protocol":"https","path":["livepro-api","ask-ai"],"host":["help","livepro","com","au"],"query":[{"key":"query","value":"how to create a document note"}],"variable":[]}},"response":[{"id":"c245cca7-8082-4645-8ce4-679247d445bd","name":"Ask AI","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://help.livepro.com.au/livepro-api/ask-ai?query=how to create a document note","protocol":"https","host":["help","livepro","com","au"],"path":["livepro-api","ask-ai"],"query":[{"key":"query","value":"how to create a document note"}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":null,"cookie":[],"responseTime":null,"body":"{\n \"can_answer\": true,\n \"answer\": \"\\nTo create a document note, click the Create button on the top right navigation bar 4196. In the Create Knowledge pop-up box, select \\\"Document Note\\\" as the Type and the default Workflow 4196. Click Continue, then populate the Knowledge Object Details with all relevant information 4196. Use the WYSIWYG editor in the Content tab to create your content 4196. Click Save at the top right of the document note 4196. In the Version pop-up box, enter comments detailing what changes have occurred 4196. Click Confirm to save the page 4196.\\n\",\n \"query\": \"how to create a document note\"\n}"}],"_postman_id":"7d2b2965-f420-4633-af0a-fc420f7979de"}],"id":"6070088e-fd68-40ce-b419-c15bdbd475e0","_postman_id":"6070088e-fd68-40ce-b419-c15bdbd475e0","description":"","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]},"isInherited":true,"source":{"_postman_id":"ae24798c-758d-44b1-8326-334014a1ddf7","id":"ae24798c-758d-44b1-8326-334014a1ddf7","name":"livepro webanswers api","type":"collection"}}}],"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":""}]}},"event":[{"listen":"prerequest","script":{"id":"470c489c-ee39-4a02-a43d-90940a13e017","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"7e6e2f99-bdfc-4de4-9bf7-dd98622eff9f","type":"text/javascript","exec":[""]}}]}