Datasets:
query_id
stringlengths 36
36
| query
stringlengths 20
119
| retrievals
listlengths 1
126
|
|---|---|---|
0ae94217-c6a0-4895-83a2-841a95f01637
|
create DevRev ticket from Microsoft Teams
|
[
{
"id": "ART-4216_KNOWLEDGE_NODE-26",
"text": "DevRev Object | Sync to DevRev |\\n| --- | --- | --- |\\n| Plan | Parts | \\xe2\\x9c\\x85 |\\n| User | Identity/DevUser | \\xe2\\x9c\\x85 |\\n| Channel | Chat | \\xe2\\x9c\\x85 |\\n| Attachments in Message/Thread/Task | Artifacts on Article | \\xe2\\x9c\\x85 |\\n| Message | Comment | \\xe2\\x9c\\x85 |\\n| Thread | Comment | \\xe2\\x9c\\x85 |\\n| Task | Issue/Ticket | \\xe2\\x9c\\x85 |\\n\\nImporting from Microsoft Teams\\n------------------------------\\n\\nFollow the steps below to import from Microsoft Teams:\\n\\n1. Go to",
"title": "Microsoft Teams AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-4216_KNOWLEDGE_NODE-29",
"text": "with many\\nattachments. DevRev honors the Microsoft Graph API rate limits and back-off and resumes automatically.\\n\\nPost import options\\n-------------------\\n\\nAfter a successful import, you have the following options available for the imported account:\\n\\n* **Sync to DevRev** \\n This option allows you to synchronize any modifications made in Microsoft Teams with the corresponding items previously imported into DevRev. It also creates new items in DevRev for any new data in Microsoft Teams",
"title": "Microsoft Teams AirSync | AirSync | Snap-ins | DevRev"
}
] |
d0b209b3-6cea-46d8-bfac-bd0e286ea21b
|
workflow builder auto close ticket after 48 hours no customer response
|
[
{
"id": "ART-2012_KNOWLEDGE_NODE-24",
"text": "customer comments on permanently closed tickets. It allows you to configure the time after which a ticket stage should be marked as closed and creates a new follow-up ticket along with all the attachments and a custom message to let the customers know that the ticket is permanently closed automatically if required.\\n\\nFor more information, refer to the [Follow-up ticket snap-in](https://marketplace.devrev.ai/followup?) on the DevRev marketplace.\\n\\nLet\\xe2\\x80\\x99s say your ticket has the",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2009_KNOWLEDGE_NODE-28",
"text": "ticket's stage when linked issue is linked or unlinked.\\n* Close pending tickets if they have remained in the *Awaiting customer response* stage for longer than x days.\\n* Update ticket's stage to waiting on user when user reverts on new conversation.\\n* Update ticket's stage to *Accepted* and notify owner and customers when an enhancement in ideation stage is linked.\\n* Update a spam conversation's stage to *Suspended*.\\n* Update a spam ticket's stage to",
"title": "Convergence | Automate | Snap-ins | DevRev"
}
] |
40c1aa6f-cd21-46ab-8f6f-76fdc267b584
|
automated reminder to customer ticket will be closed in 4 days
|
[
{
"id": "ART-3068_KNOWLEDGE_NODE-24",
"text": "[Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Conversation reminder](/docs/automations/conversation-reminder)\\n\\nConversation reminder\\n=====================\\n\\nThe Conversation Reminder Snap-in is designed to automatically send a\\nnotification to the customer who initiated the conversation if it remains in\\n\"Waiting on User\" stage for an extended period, as defined in the configured\\ntime settings. The notification message sent to the customer can be",
"title": "Conversation reminder | Automate | Snap-ins | DevRev"
},
{
"id": "ART-3068_KNOWLEDGE_NODE-25",
"text": "customized\\nduring the installation of the Snap-in, allowing for tailored communication\\naccording to specific requirements.\\n\\n![]()\\n\\nFor more information, refer to the\\n[Conversation Reminder snap-in](https://marketplace.devrev.ai/conversation-reminder)\\non the DevRev marketplace.\\n\\nInstalling the auto parts to conversation snap-in\\n-------------------------------------------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore\\n Marketplace** in the top-right",
"title": "Conversation reminder | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1284_KNOWLEDGE_NODE-16",
"text": "false |\\n| 20 | end |\\n| 21 | else false |\\n| 22 | end |\\n```\\n\\nScheduled events\\n----------------\\n\\n`flow-events` are an event source that snap-ins can use to publish or schedule events directly. This event source can then be used to trigger another automation. This capability makes it ideal for building snap-ins that need to act later. For example, sending reminders to issues still in the *Triage* stage.\\n\\nYou create an event source of type `flow-events`, and from your snap-in, you call",
"title": "Event sources | DevRev | Docs"
}
] |
e47d883f-b712-4f98-bd06-14ade143e3c2
|
connect Bitbucket account to DevRev account
|
[
{
"id": "ART-2030_KNOWLEDGE_NODE-27",
"text": "**Explore Marketplace** in the top-right corner.\\n2. In the DevRev marketplace, find **Bitbucket for DevRev** and click **Install**.\\n3. During the snap-in installation, follow the instructions for installing the webhook. The webhook can be installed for an entire Bitbucket org or specific repositories. If you install the webhook successfully, the message \"Webhook installed successfully\" is displayed in the\\xc2\\xa0**Discussions**\\xc2\\xa0tab. If it was not installed correctly, you could see",
"title": "Bitbucket | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2030_KNOWLEDGE_NODE-26",
"text": "IDE.\\n* **Autotrack work**: Automatically track your work in DevRev even without creating an issue ahead of time.\\n* **PR task creation**: Create DevRev tasks for PR reviewers.\\n* **PR reminders**: Automatically remind PR reviewers when a PR goes stale.\\n\\n![]()\\n\\nFor more information, refer to the\\n[Bitbucket for DevRev snap-in](https://marketplace.devrev.ai/bitbucket) on the DevRev marketplace.\\n\\nInstallation\\n------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click",
"title": "Bitbucket | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2030_KNOWLEDGE_NODE-40",
"text": "to\\xc2\\xa0**Settings**\\xc2\\xa0>\\xc2\\xa0**Account**\\xc2\\xa0>\\xc2\\xa0**External Identities**\\xc2\\xa0and\\xc2\\xa0**Link Bitbucket Account**.\\n\\nPR reminders\\n------------\\n\\nPRs can often go stale and delay the development process. With PR reminders, developers can be automatically notified when a PR has been inactive for a period of time.\\n\\nTo make use of this feature, the following conditions must be met:\\n\\n1. Enable the **Send reminders for inactive PRs** feature in the\\xc2\\xa0snap-in in your",
"title": "Bitbucket | Integrate | Snap-ins | DevRev"
}
] |
2e6f9413-15ac-4974-a380-7aa22fc98a61
|
use of workflows in DevRev
|
[
{
"id": "ART-1961_KNOWLEDGE_NODE-28",
"text": "workflow engine.\\n* **Automations on one schema**: Our AirSync feature automatically transforms data from different sources. It enables you to create workflows natively in DevRev without the need to create fetch nodes or manually transform data.\\n\\nComponents\\n----------\\n\\n* Workflow canvas: The field where you connect and visualize different steps in your workflow.\\n* Steps: The building blocks of your workflow, shown on the canvas.\\n* Variable selector: Used to insert variables into your",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-24",
"text": "[Creating a workflow](#creating-a-workflow)\\n* [Workflow example: Ticket auto-response](#workflow-example-ticket-autoresponse)\\n\\n1. [Documentation](/docs)\\n3. [Computer by DevRev](/docs/intro)\\n[Workflows](/docs/product/workflow-engine)\\n\\nWorkflows\\n=========\\n\\nA workflow is a series of triggers, actions, and conditions designed to achieve a specific goal or outcome. Depicted as a flowchart or diagram, it illustrates how various triggers and actions interconnect.\\n\\nDevRev\\xe2\\x80\\x99s",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-4179_KNOWLEDGE_NODE-3",
"text": "the DevRev ecosystem.](https://devrevu.reach360.com/share/course/676d4cd1-0520-45bd-813d-8289d0fc8772)[![]()\\n\\nDevRev: Customizations and snap-ins\\n\\nExtend DevRev by building custom experiences for your workflow](https://devrevu.reach360.com/share/course/6dea13c5-5e05-46bd-bf2b-e29f4fca130c)[![]()\\n\\nDevRev: Workflows and automations\\n\\nDesign workflows and automations that drive productivity at",
"title": "DevRev University"
},
{
"id": "ART-2076_KNOWLEDGE_NODE-3",
"text": "the DevRev ecosystem.](https://devrevu.reach360.com/share/course/676d4cd1-0520-45bd-813d-8289d0fc8772)[![]()\\n\\nDevRev: Customizations and snap-ins\\n\\nExtend DevRev by building custom experiences for your workflow](https://devrevu.reach360.com/share/course/6dea13c5-5e05-46bd-bf2b-e29f4fca130c)[![]()\\n\\nDevRev: Workflows and automations\\n\\nDesign workflows and automations that drive productivity at",
"title": "DevRev University"
},
{
"id": "ART-3038_KNOWLEDGE_NODE-9",
"text": "workflows in DevRev to automatically categorize work. They connected GitHub effortlessly, enabling stage changes to update without manual effort. With Dev360, integrated directly into DevRev, they analyze developer productivity and track velocity in real time. They also rely on advanced project tracking inside our app to manage large-scale engineering initiatives with greater visibility.\\n\\nTogether, these integrations and capabilities embody the convergence of Dev + Rev, giving Bolt a single",
"title": "Bolt unifies support and product to deliver seamless commerce"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-32",
"text": "issues, or custom objects) is supported via the DevRev API.\\n\\nYou can use the API to create, update, or reorder stages in your workflow.\\n\\nThe endpoint and payload depend on the object type (ticket, issue, custom object, etc.).\\n\\nIf you share which object\\xe2\\x80\\x99s stages you want to customize, I can provide a sample API call or payload.Analytics and Reporting\\n\\n1. Creating Reports in DevRev\\n\\nYou can create reports in DevRev by building dashboards with widgets:\\n\\nGo to the Vista you",
"title": "Support queries related playbook"
},
{
"id": "ART-16784_KNOWLEDGE_NODE-19",
"text": "[https://devrev.ai/docs/product/core](https://devrev.ai/docs/product/core)vista\\n\\nA list of objects in DevRev that you can sort, categorize, and share.\\n\\nRead more about vista: [https://devrev.ai/docs/product/vistas](https://devrev.ai/docs/product/vistas)workflow\\n\\nA series of triggers, actions, and conditions designed to achieve a specific goal or outcome.\\n\\nDepicted as a flowchart or diagram, a workflow illustrates how various triggers and actions interconnect.\\n\\nRead more about",
"title": "Glossary"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-33",
"text": "account.\\n\\n**Ask AI**\\n\\nWrite your own LLM prompt to generate content that can be used in various contexts. For example, you can request a summary of a ticket based on the title and description.\\n\\nCreating a workflow\\n-------------------\\n\\n1. Go to [**Settings** > **Workflows**](https://app.devrev.ai/devrev/settings/workflows?labels=skill&labelsOp=not_any&status=active). A canvas appears.\\n2. Enter a name for your workflow.\\n3. Select the steps you want to include by selecting them from the",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1710_KNOWLEDGE_NODE-9",
"text": "everyone in real time. This transparency has improved decision-making and operational efficiency across the organization. DevRev\\xe2\\x80\\x99s seamless migration and workflow creation have eliminated the need for external automations, Jira connectors, and additional Slack integrations. We now conduct our meetings by screen sharing the DevRev app, sorting and grouping columns, and voila, we have the information we want to present, reducing the time spent on operational tasks.\\n\\n![]()\\n\\nJishnu",
"title": "Yellow.ai uses DevRev to Streamline Processes"
},
{
"id": "ART-16784_KNOWLEDGE_NODE-20",
"text": "workflow: [https://devrev.ai/docs/product/workflow-engine](https://devrev.ai/docs/product/workflow-engine)workspace\\n\\nThe customer of a product or service.\\n\\nRead more about workspace: [https://devrev.ai/docs/product/customers](https://devrev.ai/docs/product/customers)'",
"title": "Glossary"
},
{
"id": "ART-17181_KNOWLEDGE_NODE-8",
"text": "notifications, while going far beyond with advanced workflows, SLA management, automation, and hybrid search functionality. The platform empowered agents to build automations themselves without relying on product teams, with Raj noting that a typical ticket lifecycle requires approximately 15 workflows, which DevRev makes practical and manageable.\\n\\nKey implementation highlights included a Lumary integration that automated customer association in 15 seconds for approximately 30% of APAC ticket",
"title": "Skedulo reduced effort 30% to 5% and unlocked automation at scale"
},
{
"id": "ART-4179_KNOWLEDGE_NODE-2",
"text": "applications](https://rise.articulate.com/share/yTvcdwN0dMgzhiU_Kgbbs2t8lfkpnC5O)[![]()\\n\\nDevRev: Admin management and set-up\\n\\nSet up, manage, and streamline workflows for smooth operations](https://devrevu.reach360.com/share/course/d238d6fd-ab6a-41b3-a99b-44e1d2a8d221)\\n\\nExplore more courses\\n--------------------\\n\\nDiscover more courses to expand your DevRev skills and continue your learning journey\\n\\n[![]()\\n\\nDevRev platform fundamentals\\n\\nYour first step to navigating and mastering",
"title": "DevRev University"
},
{
"id": "ART-2076_KNOWLEDGE_NODE-2",
"text": "applications](https://rise.articulate.com/share/yTvcdwN0dMgzhiU_Kgbbs2t8lfkpnC5O)[![]()\\n\\nDevRev: Admin management and set-up\\n\\nSet up, manage, and streamline workflows for smooth operations](https://devrevu.reach360.com/share/course/d238d6fd-ab6a-41b3-a99b-44e1d2a8d221)\\n\\nExplore more courses\\n--------------------\\n\\nDiscover more courses to expand your DevRev skills and continue your learning journey\\n\\n[![]()\\n\\nDevRev platform fundamentals\\n\\nYour first step to navigating and mastering",
"title": "DevRev University"
},
{
"id": "ART-1945_KNOWLEDGE_NODE-29",
"text": "such as Slack and Jira. Automations perform tasks within DevRev based on events, like responding to customer conversations and linking tickets and issues. [AirSync](./import) helps you bring data from external sources to DevRev and keep them in sync.\\n\\nWhile numerous snap-ins are available and more are in development, you can create your own using [DevRev APIs](https://developer.devrev.ai/about/for-developers).\\n\\n[PreviousIntroduction](/docs)[NextCore concepts](/docs/product/core)\\n\\n#### On",
"title": "Computer by DevRev | DevRev"
},
{
"id": "ART-1027_KNOWLEDGE_NODE-9",
"text": "workflows** that streamline ticket triaging and severity assessment.\\n\\n### AI-powered deflection at scale\\n\\nAI answering has stabilized around 32\\xe2\\x80\\x9340% of all inquiries, with complex queries intelligently routed to human agents. **Computer CX Agents** for free vs. paid customers optimize deflection strategies for each segment, delivering tailored support while maximizing efficiency.\\n\\nDevRev has enabled us to streamline access to technical documentation, automate common developer",
"title": "Descope streamlines support at scale with automation, AI, and unified collaboration"
},
{
"id": "ART-12391_KNOWLEDGE_NODE-27",
"text": "workflow.\\n\\nNow, your workflow runs whenever a conversation or a ticket gets created and it\\nassigns it to an AI agent, which handles the conversation. No brittle rules.\\n\\nFind below a detailed explanation of all the fields needed to configure in the\\n\"Talk to Agent\" Step\\n\\n| Parameter | Type | Description |\\n| --- | --- | --- |\\n| agent | String | ID of the AI agent to use. Use the dropdown to select one. |\\n| object | String | ID of the conversation or ticket where the agent operate.s |\\n|",
"title": "Conversational workflows | Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-30",
"text": "Action: Tasks that modify one or more objects in the system.\\n* Control: Conditional (if-then) blocks to determine which actions to take based on an operand (variable) and an operator.\\n* Delay: Wait to take an action.\\n\\nAI nodes\\n--------\\n\\nWe provide several native AI nodes out of the box to enhance your workflows.\\n\\n**Spam checker**\\n\\nThe spam checker takes the ID of a ticket or object and determines whether the ticket or conversation is spam. You can use this output in your workflows as",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-15617_KNOWLEDGE_NODE-12",
"text": "systems\\n\\nDevRev : AI-powered search draws on past conversations and external data\\n\\nDevRev : Built-in AI can dedupe, cluster, classify, route, generate, and attribute information\\n\\nPylon : AI agents constrained to internal data only, no external system access\\n\\nCustom Workflows\\n\\nDevRev : AI decision nodes for intelligent workflow routing based on context\\n\\nDevRev : No-code workflow building with simple prompts and easy import capabilities\\n\\nDevRev : Track customer sentiment in",
"title": "Pylon - Competitive - for the PLuG on website"
},
{
"id": "ART-15792_KNOWLEDGE_NODE-2",
"text": "structured around two critical business dimensions: Products (Dev) and Customers (Rev). This architectural approach ensures that AI agents have comprehensive context when making decisions or taking actions.\\n\\nAgentic AI capabilities: DevRev provides both out-of-the-box agents and an Agent Studio to build, customize, deploy and manage agents. Users can instruct these agents in plain language to execute complex workflows autonomously, with agents capable of creating tickets, updating records,",
"title": "DevRev Products and Agents"
},
{
"id": "ART-1036_KNOWLEDGE_NODE-12",
"text": "\\xe2\\x80\\x93 workflows for automation and sentiment-based prioritization\\n* Computer Memory \\xe2\\x80\\x93 unified knowledge graph\\n* Knowledge base management with Smart Import capabilities\\n* Team inbox for customer conversations\\n* Automated ticket creation and management\\n* Unified platform for conversations, tickets, and issues\\n* Native DevRev-Jira integration\\n* SLA management\\n* Role-based authorization\\n\\nDevRev not just helped implement their Support app but also guided us in improving",
"title": "Shipsy elevates logistics support with AI-powered automation and cross team collaboration"
},
{
"id": "ART-12390_KNOWLEDGE_NODE-25",
"text": "library\\n=======================\\n\\nWhen a workflow starts running, the action steps define which operations or\\nprocesses occur and specify any data that needs to be transferred between\\nblocks. Below is a list the action steps you can use.\\n\\nObject creation\\n---------------\\n\\n| Operation | Description | Input Parameters | Output |\\n| --- | --- | --- | --- |\\n| Create Account | Creates a new account in DevRev. | * Account details like name, description, domains, etc. * subtype: (Optional)",
"title": "Workflow action library | Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1960_KNOWLEDGE_NODE-44",
"text": "about\\xc2\\xa0[*vista*](https://docs.devrev.ai/product/vistas)\\n\\nworkflow\\n\\n: A series of triggers, actions, and conditions designed to achieve a specific goal or outcome.\\n: Depicted as a flowchart or diagram, a workflow illustrates how various triggers and actions interconnect.\\n: Read more about\\xc2\\xa0[*workflow*](https://devrev.ai/docs/product/workflow-engine)\\n\\nworkspace\\n\\n: The customer of a product or service.\\n: Read more",
"title": "Glossary | Computer by DevRev | DevRev"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-2",
"text": "on the DevRev platform.\\nA webhook can be thought of as a \\xe2\\x80\\x98reverse API\\xe2\\x80\\x99 that\\xe2\\x80\\x99s driven by events rather than requests. While APIs are used to pull data from the system, webhooks are a mechanism for the system to push data to a pre-configured endpoint.\\nWebhooks allow you to receive notifications based on events without having to explicitly make a request.\\n\\nWebhook workflow\\n----------------\\n\\nYou must first set up an HTTP server that listens on a publicly",
"title": "Webhooks | DevRev | Docs"
}
] |
84fac619-f780-4343-960b-1b6c735f4c1f
|
workflow send email when boolean field set to true
|
[
{
"id": "ART-4020_KNOWLEDGE_NODE-24",
"text": "[Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Send customized emails](/docs/automations/send-emails)\\n\\nSend customized emails\\n======================\\n\\nThe [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) snap-in automates email sending. Once activated, this operation becomes available in the Workflow builder, enabling the delivery of personalized messages.\\n\\nConfiguration\\n-------------\\n\\n1. Create a **SendGrid**",
"title": "Send customized emails | Automate | Snap-ins | DevRev"
},
{
"id": "ART-4020_KNOWLEDGE_NODE-25",
"text": "account.\\n2. Generate an **API key**.\\n3. Create a SendGrid connection:\\n a. Go to **Settings** > **Snap-ins** > **+ Connection**\\n b. Select **SendGrid**.\\n c. Add the **API key** and click **Save**.\\n\\nInstallation\\n------------\\n\\n1. Install the [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) from the DevRev marketplace.\\n2. Open the Workflow Builder and locate the **send customized emails** action node.\\n3. Configure the node by selecting the",
"title": "Send customized emails | Automate | Snap-ins | DevRev"
}
] |
09ff15cd-16ce-457d-ab30-56dc3d9f3f37
|
recorded training session on Ticket-SLA Analytics
|
[
{
"id": "ART-4177_KNOWLEDGE_NODE-6",
"text": "through tickets](https://vimeo.com/1027660342)[![]()\\n\\nUnderstanding Support Analytics and SLAs\\n\\nExplore actionable insights and trends in customer experience metrics with our support analytics dashboard](https://vimeo.com/1027659562)[![]()\\n\\nInteractive walkthrough of SLA tracking\\n\\nLearn how to use DevRev track SLAs of tickets, to ensure that your customer's requests are always responded to in time.](https://devrev.navattic.com/bv10lxn)\\n\\nBuild Products, Not",
"title": "DevRev University - DevRev for Startups"
}
] |
f520802b-15ce-461b-a05c-9273a103d7da
|
session missing when user sends video recording
|
[
{
"id": "ART-4186_KNOWLEDGE_NODE-43",
"text": "app.\\n* Unlike web sessions, there is **no time limit** on session length.\\n* A session contains multiple **recordings**:\\n + A **recording** ends when the app is backgrounded.\\n + A **new recording** starts when the app comes to the foreground again.\\n + The **session ends** when the app is killed, or it crashes, or it becomes non-responsive, or after 30 mins of inactivity.\\n + Sessions are **uploaded** the next time the app is launched.\\n\\nSession Analytics: Mobile dashboard consists of",
"title": "Computer for User Insights | Session analytics | Computer for Your Customers | DevRev"
},
{
"id": "ART-12449_KNOWLEDGE_NODE-22",
"text": "session recording to capture user interactions with your app.\\n\\n#####\\n\\nThe session recording feature is opt-out and is enabled by default.\\n\\nHere are the available methods to help you control the session recording feature:\\n\\nAction| Kotlin (`DevRev`)| Java (`DevRevObservabilityExtKt`) \\n---|---|--- \\nStarts the session recording.| startRecording()| startRecording(DevRev.INSTANCE, context); \\nEnds the session recording and uploads it to the portal.| stopRecording()|",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-2898_KNOWLEDGE_NODE-19",
"text": "app.\\n\\n#####\\n\\nThe session recording feature is opt-out and is enabled by default.\\n\\nHere are the available methods to help you control the session recording feature:\\n\\nAction| Kotlin (`DevRev`)| Java (`DevRevObservabilityExtKt`) \\n---|---|--- \\nStarts the session recording.| startRecording()| startRecording(DevRev.INSTANCE, context); \\nEnds the session recording and uploads it to the portal.| stopRecording()| stopRecording(DevRev.INSTANCE); \\nPauses the ongoing session recording.|",
"title": "Android integration — DevRev | Docs"
},
{
"id": "ART-15513_KNOWLEDGE_NODE-33",
"text": "`DevRev.startRecording()` | Starts the session recording. |\\n| `DevRev.stopRecording()` | Ends the session recording and uploads it to the portal. |\\n| `DevRev.pauseRecording()` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording()` | Resumes a paused session recording. |\\n| `DevRev.processAllOnDemandSessions()` | Stops the ongoing user recording and sends all on-demand sessions along with the current recording. |\\n\\nUsing this property returns the status of the session",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2898_KNOWLEDGE_NODE-18",
"text": "this user.\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.resumeAllMonitoring() \\n ---|---\\n[/code] \\n \\nIf session recording was disabled for the user using the `stopAllMonitoring()` method, you can enable recording at runtime with this method.\\n\\n#####\\n\\nThis feature only stores a monitoring permission flag and does not provide any user interface or dialog.\\n\\n### Session recording\\n\\nYou can enable session recording to capture user interactions with your",
"title": "Android integration — DevRev | Docs"
},
{
"id": "ART-15515_KNOWLEDGE_NODE-33",
"text": "|\\n| `DevRev.pauseRecording()` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording()` | Resumes a paused session recording. |\\n| `DevRev.processAllOnDemandSessions()` | Stops the ongoing user recording and sends all on-demand sessions along with the current recording. |\\n\\nYou can also check the following flags for session recording:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | // Check if session recording is currently active. |\\n| 2 | let isRecording = DevRev.isRecording |\\n| 3 |",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-12398_KNOWLEDGE_NODE-33",
"text": "enable_session_recording: true,\\n\\n\\n\\n5 session_recording_options: {\\n\\n\\n\\n6 sessionDetails: {\\n\\n\\n\\n7 sessionId: sessionId,\\n\\n\\n\\n8 tabId: tabId,\\n\\n\\n\\n9 },\\n\\n\\n\\n10 },\\n\\n\\n\\n11 });\\n```\\n\\nShow more\\n```\\n\\nYou can leave the tabId empty if you want to track this domain as a separate tab within the same session.\\n\\n![]()\\n\\nIf the session identifiers passed to the Plug method correspond to a session which has already ended, or some invalid identifiers, the SDK",
"title": "Cross-domain session tracking | Session analytics | Computer for Your Customers | DevRev"
},
{
"id": "ART-4255_KNOWLEDGE_NODE-19",
"text": "recording.| startRecording()| startRecording(DevRev.INSTANCE, context); \\nEnds the session recording and uploads it to the portal.| stopRecording()| stopRecording(DevRev.INSTANCE); \\nPauses the ongoing session recording.| pauseRecording()| pauseRecording(DevRev.INSTANCE); \\nResumes a paused session recording.| resumeRecording()| resumeRecording(DevRev.INSTANCE); \\n \\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the",
"title": "DevRev SDK for Android — DevRev | Docs"
},
{
"id": "ART-2982_KNOWLEDGE_NODE-15",
"text": "\\nTo opt back in, use the following method:\\n\\n[code]\\n\\n 1| DevRev.resumeAllMonitoring() \\n ---|---\\n[/code] \\n \\n### Session recording\\n\\nYou can enable session recording to capture user interactions with your app.\\n\\n#####\\n\\nThe session recording feature is opt-out and is enabled by default.\\n\\nThe session recording feature includes the following methods to control the recording:\\n\\nMethod| Action \\n---|--- \\n`DevRev.startRecording()`| Starts the session recording.",
"title": "React Native integration — DevRev | Docs"
},
{
"id": "ART-4256_KNOWLEDGE_NODE-14",
"text": "out\\n\\nSession analytics features are opted-in by default, enabling them from the start. However, you can opt-out using the following method:\\n\\n[code]\\n\\n 1| DevRev.stopAllMonitoring() \\n ---|---\\n[/code] \\n \\nTo opt back in, use the following method:\\n\\n[code]\\n\\n 1| DevRev.resumeAllMonitoring() \\n ---|---\\n[/code] \\n \\n### Session recording\\n\\nYou can enable session recording to record user interactions with your app.\\n\\n#####\\n\\nThe session recording feature is opt-out and",
"title": "DevRev SDK for React Native — DevRev | Docs"
},
{
"id": "ART-15507_KNOWLEDGE_NODE-28",
"text": "`DevRev.pauseRecording()` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording()` | Resumes a paused session recording. |\\n| `DevRev.processAllOnDemandSessions()` | Stops the ongoing user recording and sends all on-demand sessions along with the current recording. |\\n\\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the session. The properties are defined as a map of string values.\\n\\n```\\n| | |\\n| --- |",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2664_KNOWLEDGE_NODE-27",
"text": "your\\n [website](https://developer.devrev.ai/sdks/web/installation) or\\n [mobile app](https://developer.devrev.ai/sdks/mobile).\\n2. For web applications, configure\\n [user identification](https://developer.devrev.ai/sdks/web/user-identity).\\n3. Enable session recording for your users, go to **Settings** > **PluG and Portal** >\\n **Session Replays** and enable recording for your desired platform.\\n\\n **Note**: Alternatively, you can enable session recording during Plug SDK\\n",
"title": "Session analytics | Computer for Your Customers | DevRev"
},
{
"id": "ART-16579_KNOWLEDGE_NODE-29",
"text": "recording. |\\n| `DevRev.stopRecording()` | Ends the session recording and uploads it to the portal. |\\n| `DevRev.pauseRecording()` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording()` | Resumes a paused session recording. |\\n| `DevRev.processAllOnDemandSessions()` | Stops the ongoing session recording and uploads all offline sessions on demand, including the current one. |\\n\\n### Session properties\\n\\nYou can add custom properties to the session recording to help you",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-12449_KNOWLEDGE_NODE-20",
"text": "enabling them from the start. However, you can opt-out using the following method:\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.stopAllMonitoring() \\n ---|---\\n[/code] \\n \\nTo opt back in, use the following method:\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.resumeAllMonitoring() \\n ---|---\\n[/code] \\n \\nYou can check whether session monitoring has been enabled by using this property:\\n\\nIf session recording was disabled for the user using the",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-12453_KNOWLEDGE_NODE-20",
"text": "Opting-in or out\\n\\nSession analytics features are opted-in by default, enabling them from the start. However, you can opt-out using the following method:\\n\\n[code]\\n\\n 1| DevRev.stopAllMonitoring() \\n ---|---\\n[/code] \\n \\nTo opt back in, use the following method:\\n\\n[code]\\n\\n 1| DevRev.resumeAllMonitoring() \\n ---|---\\n[/code] \\n \\n### Session recording\\n\\nYou can enable session recording to capture user interactions with your app.\\n\\n#####\\n\\nThe session recording feature",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-28",
"text": "calling the `shutdown()` method will stop the ongoing session recording. Re-initializing with the `init()` method will then start a new session recording. To avoid losing continuity, you can pass the details of the ongoing session recording when re-initializing Plug.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | // Get the ongoing session details |\\n| 2 | const { sessionId, tabId } = window.plugSDK.getSessionDetails(); |\\n| 3 | |\\n| 4 | if (window.plugSDK.isPlugInitialized) { |\\n| 5 |",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-29",
"text": "window.plugSDK.shutdown(); |\\n| 6 | } |\\n| 7 | window.plugSDK.init({ |\\n| 8 | app_id: appId, |\\n| 9 | |\\n| 10 | // Pass the session details |\\n| 11 | session_recording_options: { |\\n| 12 | sessionDetails: { |\\n| 13 | sessionId: sessionId, |\\n| 14 | tabId: tabId, |\\n| 15 | }, |\\n| 16 | }, |\\n| 17 | |\\n| 18 | // With session token |\\n| 19 | session_token: sessionToken, |\\n| 20 | // Or without session token |\\n| 21 | identity: {}, |\\n| 22 | }); |\\n```\\n\\nWas this page",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-4257_KNOWLEDGE_NODE-20",
"text": "Action \\n---|--- \\n`DevRev.startRecording()`| Starts the session recording. \\n`DevRev.stopRecording()`| Ends the session recording and uploads it to the portal. \\n`DevRev.pauseRecording()`| Pauses the ongoing session recording. \\n`DevRev.resumeRecording()`| Resumes a paused session recording. \\n \\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the session. The properties are defined as a dictionary of string",
"title": "DevRev SDK for iOS — DevRev | Docs"
},
{
"id": "ART-15515_KNOWLEDGE_NODE-34",
"text": "|\\n| 4 | // Check if session monitoring is enabled. |\\n| 5 | let isMonitoringEnabled = DevRev.isMonitoringEnabled |\\n| 6 | |\\n| 7 | // Check if on-demand sessions are enabled. |\\n| 8 | let areOnDemandSessionsEnabled = DevRev.areOnDemandSessionsEnabled |\\n```\\n\\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the session. The properties are defined as a dictionary of string values.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 |",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2895_KNOWLEDGE_NODE-2",
"text": "view their past conversations. Identifying your users also enables more personalized engagement.\\n\\nIn this flow, you have to generate a session token for every user who visits your website. The session token identifies the customer when they interact with the widget. The session token is generated using the application access token and customer information. It should be generated on your website\\xe2\\x80\\x99s back end since the app token needs to be kept hidden.\\n\\nTo identify logged-in users,",
"title": "Identify your users with PLuG — DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-5",
"text": "(True or False) |\\n| `session_recording_key` | Identifies your session recording account and is required to enable the SDK session recording features. | String |\\n| `enable_session_recording` | Instructs the widget to determine whether to start the session recording. | Boolean (True or False) |\\n| `session_token` | Identifies the user interacting with your app. | String |\\n| `primary_text_color` | The color of the launcher, button text for new tickets and conversations, conversation user text,",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-12398_KNOWLEDGE_NODE-27",
"text": "method to fetch these ids.\\n\\n```\\n```\\n1 const { sessionId, tabId } = window.plugSDK.getSessionDetails();\\n```\\n```\\n\\n![]()\\n\\nTo ensure that the session recording features are ready before calling getSessionDetails, wait on the ON\\\\_OBSERVABILITY\\\\_READY Plug event. For more information about this event, refer to the [methods reference](https://developer.devrev.ai/public/sdks/web/methods).\\n\\n```\\n```\\n1 window.plugSDK.onEvent(payload => {\\n\\n\\n\\n2 if (payload.type ===",
"title": "Cross-domain session tracking | Session analytics | Computer for Your Customers | DevRev"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-3",
"text": "engagement.\\n\\nTo implement user identification, you need to generate a session token for each user who visits your website. This token is created using your application access token combined with customer information, and must be generated on your backend to keep the application token secure.\\n\\nDevRev\\'s BackendYour BackendYour FrontendYour UserDevRev\\'s BackendYour BackendYour FrontendYour User(1) User is known(via Signup, Login)(2) Send user details(3) auth-tokens.create API call(4) Return",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-24",
"text": "\"Credit Card\", \\n 6| \"expiry_date\" : \"2024-12-12\" \\n 7| } \\n 8| window.plugSDK.trackEvent(\"signed_up\",properties)\\n[/code] \\n \\nTo learn more about tracking events, visit [Track events](/public/sdks/web/track-events).\\n\\n## Restart session recording\\n\\nThe `restartSessionRecording` method is used to restart session recording.\\n\\n[code]\\n\\n 1| window.plugSDK.restartSessionRecording(); \\n ---|---\\n[/code] \\n \\nWas this page helpful?YesNo\\n\\n[Custom implementationUp",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-2898_KNOWLEDGE_NODE-17",
"text": "DevRev SDK offers session analytics features to help you understand how users interact with your app.\\n\\n### Opt in or out\\n\\nEnd users can opt in or out of the session analytics feature, enabling them to control whether their interactions are tracked for analytics.\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.stopAllMonitoring() \\n ---|---\\n[/code] \\n \\nThis method terminates and deletes the current session recording and also disables future session recording by our SDK for",
"title": "Android integration — DevRev | Docs"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-27",
"text": "|\\n| 1 | // Delete the existing Plug instance if it exists |\\n| 2 | if (window.plugSDK.isPlugInitialized) { |\\n| 3 | window.plugSDK.shutdown(); |\\n| 4 | } |\\n| 5 | |\\n| 6 | // Re-initialize Plug |\\n| 7 | window.plugSDK.init({ |\\n| 8 | app_id: appId, |\\n| 9 | |\\n| 10 | // With session token |\\n| 11 | session_token: sessionToken, |\\n| 12 | |\\n| 13 | // Or without session token |\\n| 14 | identity: {}, |\\n| 15 | }); |\\n```\\n\\nIf you\\xe2\\x80\\x99re using the Plug SDK for recording user sessions,",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-6",
"text": "\\n`enable_default_launcher`| Show/hide the default PLuG widget launcher.| Boolean (True or False) \\n`session_recording_key`| Identifies your session recording account and is required to enable the SDK session recording features.| String \\n`enable_session_recording`| Instructs the widget to determine whether to start the session recording.| Boolean (True or False) \\n`session_token`| Identifies the user interacting with your app.| String \\n`primary_text_color`| The color of the launcher,",
"title": "Methods — DevRev | Docs"
}
] |
743b1f32-0db4-4a68-8d8e-c689592f7cca
|
email notifications not received after specific time
|
[
{
"id": "ART-2027_KNOWLEDGE_NODE-45",
"text": "due to mail loops, the email integration has the provision to specify user-specific email limits. By default, the user-specific limit is set to 30 emails per 10 minutes.\\n\\nIf a user sends 30 emails in a 10-minute time frame, this particular user is marked with the tag spammer. Once marked as a spammer, the user can only send 100 emails in a 24-hour period. All of these emails are marked as spam by the system. Any emails beyond the 100 spam email default limit are dropped, and the blocked tag",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-56",
"text": "deliverable.\\n\\n5. Events Panel\\n---------------\\n\\nLocated in the top right of the Email Integration page, this opens a side panel with:\\n\\n* **Key Email Events** such as Delivery failures (bounces), Spam flagging (rate-limit violations), etc.\\n* **Internal discussion**: Collaborators can comment on specific events for shared visibility and debugging\\n\\n[PreviousEmail](/docs/integrations/email)[NextExotel](/docs/integrations/exotel)\\n\\n#### On this page\\n\\n* [1. Create a new",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-3068_KNOWLEDGE_NODE-24",
"text": "[Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Conversation reminder](/docs/automations/conversation-reminder)\\n\\nConversation reminder\\n=====================\\n\\nThe Conversation Reminder Snap-in is designed to automatically send a\\nnotification to the customer who initiated the conversation if it remains in\\n\"Waiting on User\" stage for an extended period, as defined in the configured\\ntime settings. The notification message sent to the customer can be",
"title": "Conversation reminder | Automate | Snap-ins | DevRev"
},
{
"id": "ART-16790_KNOWLEDGE_NODE-2",
"text": "to.Preferences\\n\\nHow do I change my timezone?\\n\\nGo to Settings > Preferences and look for the Timezone section. Click on the dropdown menu to search and select your preferred timezone. This affects when you receive reminders, notifications, and emails.Organization Settings\\n\\nWho can access organization settings? Organization settings are typically available to administrators who can manage team information, including the organization name, URL, data location, and member access",
"title": "Computer Settings and Preferences FAQs"
}
] |
0def0eb5-ac35-4294-8376-58f156f3c83c
|
enable sorting by a custom field in ticketing system
|
[
{
"id": "ART-1645_KNOWLEDGE_NODE-36",
"text": "fragments aren\\xe2\\x80\\x99t listed in the response.\\n\\n## Configure UI hints\\n\\nUI hints allow customizing the UI/UX of custom fields. So far, `ui.display_name` has been used to set the display name of a field. Let\\xe2\\x80\\x99s look at the other supported UI hints:\\n\\n * `display_name`: The display name of the field.\\n\\n * `is_hidden`: Whether the field is hidden.\\n\\n * `placeholder`: The placeholder text for the field.\\n\\n * `is_sortable`: Whether the field is sortable. Requires",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-34",
"text": "hints\\n------------------\\n\\nUI hints allow customizing the UI/UX of custom fields. So far, `ui.display_name` has\\nbeen used to set the display name of a field. Let\\xe2\\x80\\x99s look at the other supported UI\\nhints:\\n\\n* `display_name`: The display name of the field.\\n* `is_hidden`: Whether the field is hidden.\\n* `placeholder`: The placeholder text for the field.\\n* `is_sortable`: Whether the field is sortable. Requires `is_filterable` to be true.\\n* `is_groupable`: Whether the field is",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-15332_KNOWLEDGE_NODE-4",
"text": "\"group_name\": \"string\", |\\n| 46 | \"is_groupable\": true, |\\n| 47 | \"is_hidden\": true, |\\n| 48 | \"is_sortable\": true, |\\n| 49 | \"order\": 1, |\\n| 50 | \"placeholder\": \"string\", |\\n| 51 | \"tooltip\": \"string\", |\\n| 52 | \"unit\": \"string\", |\\n| 53 | \"use_shorthand_notation\": true |\\n| 54 | }, |\\n| 55 | \"default_value\": true |\\n| 56 | } |\\n| 57 | ], |\\n| 58 | \"description\": \"string\", |\\n| 59 | \"name\": \"string\" |\\n| 60 | } |\\n| 61 | ], |\\n| 62 | \"custom_fields\": [ |\\n| 63 | { |\\n| 64 | \"description\":",
"title": "Get Schemas Aggregated (POST) | DevRev | Docs"
},
{
"id": "ART-1957_KNOWLEDGE_NODE-33",
"text": "text**: Add a placeholder text that will be visible to the users before they enter an input.\\n * **Group name**: You can use a group name to create a group accordion for the chosen attributes.\\n * **Field visibility**: Choose how you want the field to be visible to users.\\n * **Field actionables**: Select actions that you can perform after creating a field such as grouping, filtering, and sorting.\\n * **Tooltip**: Add information about the field which will be visible when hovered",
"title": "Object customization | Computer by DevRev | DevRev"
}
] |
01661e52-e483-435f-aab5-3034a7f6c732
|
internal people can't see KB articles
|
[
{
"id": "ART-1985_KNOWLEDGE_NODE-38",
"text": "and **Public Portal**.\\n\\n### Share an article\\n\\nOnce you've created an article, you have two options to share it:\\n\\n* Use **Copy external link** to share with your customers, allowing them to access the article directly.\\n* Use **Copy internal link** to share with your internal organizational team members.\\n\\nThe ability to view the article depends on the settings for **Visible to** and **Status** that have been configured.\\n\\n* If you are sharing an external link with non-signed-in",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-36",
"text": "verified (signed-in) customers can view the article.\\n* **Verified Customers**: Limits visibility to customers signed in to the customer portal.\\n* **Customer Admins**: Restricts access to a subset of verified customers in the **Customer Admin** group. Membership in this group is managed through [**Settings** > **Customer Management** > **Segments**](https://app.devrev.ai/?setting=segments)\\\\*.\\n\\n ![]()\\n\\n If an article is for internal use only, leave the **Visible to** field blank.\\n\\n###",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-31",
"text": "verified customers.\\n4. Click **Create** and select whether you want to **Create** an article in draft mode, **Submit for review**, or **Publish**.\\n\\nTo ensure that the article is visible to your users, the **Status** of the article must be *Published* and the user group must be indicated in the **Visible to** field.\\n\\n### Edit article content and settings\\n\\nTo update the content or settings of an existing article, do the following:\\n\\n1. Go to [**Settings** > **Support** > **Knowledge",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-16192_KNOWLEDGE_NODE-29",
"text": "permissions in DevRev's articles. Only can read and can contribute permissions are imported from the knowledge base and articles.\\n* **Content & Metadata**: Imports published articles, including content, titles, dates, authors, and source URLs.\\n* **Version History**: Keeps track of published article versions.\\n* **Attachments**: Transfers files attached to articles and links them correctly.\\n* **User Criteria**: Imports users and group rules from ServiceNow.\\n\\n### Limitations\\n\\n* **Access",
"title": "ServiceNow KB AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1980_KNOWLEDGE_NODE-29",
"text": "by customers through the Plug widget and customer portal.\\n\\nIn the Plug widget, articles are available in two places: the search bar and the Help section.\\n\\n**Search bar**\\n\\n![]()\\n\\n**Help section**\\n\\n![]()\\n\\nUsers can also view articles grouped into collections by visiting your help center hosted on your website. The visibility of collections and articles depends on the **Visible to** settings configured.\\n\\n[### Articles](/docs/product/articles)[###",
"title": "Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-30",
"text": "additional settings for the article:\\n\\n * **Part** (required): Define the feature or capability the article addresses.\\n * **Owned by** (required): Assign a singular point of contact responsible for the article, aiding in management and ownership.\\n * **Status**: Indicate the current stage of the article.\\n * **Collection**: Categorize the article under a topic/theme in your customer portal.\\n * **Visible To**: Decide whether the article should be visible to all customers or only",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-17231_KNOWLEDGE_NODE-40",
"text": "article is shared and the corresponding roles. |\\n| `status` | enum | | Status of the article. |\\n| `tags` | reference (collection)\\xe2\\x86\\x92[#record:tag] | | Tags associated with the article. |\\n| `title` | text | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Title of the article. |\\n| `type` | enum | | Type of the article. |\\n| `visible_to` | enum | | |\\n\\n#### Enum values\\n\\n**access\\\\_level**\\n\\n| Value | Name | Description |\\n| --- | --- | --- |\\n| `EXTERNAL` | - | - |\\n| `INTERNAL` | - | - |\\n|",
"title": "Supported DevRev object types | DevRev | Docs"
},
{
"id": "ART-17233_KNOWLEDGE_NODE-11",
"text": "specifies the permission level for each user or group using the `permission` type.\\nThis type is a structure that connects a reference to a user-like record type (the `member_id` field)\\nwith an `enum` value that defines the user\\xe2\\x80\\x99s role or permission level.\\n\\n### Scope interaction\\n\\n###### Internal scope\\n\\n###### External scope\\n\\nFor `scope=internal` articles:\\n\\n* By default, only the owner has access.\\n* Additional access is granted exclusively through the `shared_with`",
"title": "Permissions | DevRev | Docs"
},
{
"id": "ART-17233_KNOWLEDGE_NODE-10",
"text": "\"Viewer\" |\\n| 19 | } |\\n| 20 | ] |\\n| 21 | }, |\\n| 22 | \"member_id\": { |\\n| 23 | \"refers_to\": { |\\n| 24 | \"#record:users\": {}, |\\n| 25 | \"#record:groups\": {}, |\\n| 26 | \"#record:platform_groups\": {} |\\n| 27 | } |\\n| 28 | } |\\n| 29 | } |\\n| 30 | } |\\n| 31 | } |\\n```\\n\\nArticle permissions\\n-------------------\\n\\nArticles in DevRev can be shared with individual users or groups, allowing for granular control over who can access what content.\\n\\n### Sharing mechanism\\n\\nThe `shared_with` field",
"title": "Permissions | DevRev | Docs"
},
{
"id": "ART-17230_KNOWLEDGE_NODE-5",
"text": "about products, services, and processes.\\nThey support both Markdown and HTML formats.\\n\\nArticles can include mentions to artifacts and other articles. Inline attachments must map to artifacts,\\nand article links must map to articles.\\n\\n### Managing permissions\\n\\nArticle permissions are managed through the `shared_with` field, which can reference users, groups, and platform groups.\\nRefer to the [permissions](/public/airsync/data-model/permissions) for more details.\\n\\n### Inline",
"title": "Rich text fields | DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-23",
"text": "Optional\\n\\nFilters for articles modified by any of the provided users.\\n\\nowned_by string Optional\\n\\nFilters for articles owned by any of the provided users.\\n\\nscope long Optional\\n\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\n\\nshared_with.member string Optional\\n\\nID of the group/member with whom the item is shared.\\n\\nshared_with.role string Optional\\n\\nRole ID of the group/member with whom the item is",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-17233_KNOWLEDGE_NODE-7",
"text": "object to the *platform groups* object in DevRev.\\n3. Reference your object in other fields, such as in the `shared_with` field of articles.\\n\\nShared with field\\n-----------------\\n\\nThe `shared_with` field enables you to define permissions for articles (and other objects in the future).\\nIt specifies both who can access the content and what permission level they have.\\nThis field utilizes the `permission` type to associate users or groups with their designated roles.\\n\\n### Structure\\n\\nEach",
"title": "Permissions | DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1823_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1577_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-30",
"text": "scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-16192_KNOWLEDGE_NODE-31",
"text": "articles default to English in DevRev, regardless of the original language.\\n If a user in ServiceNow belongs to two different criteria\\xe2\\x80\\x94one allowing read and contribute access, and the other denying it\\xe2\\x80\\x94they may still have access in DevRev. However, if the same criteria appear in both the allow and deny lists for read and contribute access, the user is restricted in DevRev.\\n\\nPost import options\\n-------------------\\n\\nAfter a successful import, you have the following",
"title": "ServiceNow KB AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Update — DevRev | Docs"
}
] |
6fb80a79-6784-4b96-890b-763959422bbf
|
problem resume conversation with built in bot
|
[
{
"id": "ART-4256_KNOWLEDGE_NODE-10",
"text": "following method:\\n\\n[code]\\n\\n 1| DevRev.showSupport() \\n ---|---\\n[/code] \\n \\n### Creating a new support conversation\\n\\nYou can initiate a new support conversation directly from your app. This method displays the support chat screen and simultaneously creates a new conversation.\\n\\n[code]\\n\\n 1| DevRev.createSupportConversation() \\n ---|---\\n[/code] \\n \\n### In-app link handling\\n\\nIn certain cases, tapping links in the support chat opens them in the app instead of a",
"title": "DevRev SDK for React Native — DevRev | Docs"
},
{
"id": "ART-4206_KNOWLEDGE_NODE-8",
"text": "\"event\": { |\\n| > | \"input_message\": { |\\n| > | \"message\": \"Your query to the agent\" |\\n| > | } |\\n| > | }, |\\n| > | \"session_object\": \"unique_conversation_identifier\", |\\n| > | \"webhook_target\": { |\\n| > | \"webhook\": \"don:integration:dvrv-us-1:devo/0:webhook/auCJ7By8\" |\\n| > | }, |\\n| > | \"client_metadata\": { |\\n| > | \"user_id\": \"12345\", |\\n| > | \"conversation_id\": \"conv-789\" |\\n| > | } |\\n| > | }\\' |\\n```\\n\\n##### \\n\\nThe session\\\\_object parameter is critical for maintaining conversation",
"title": "Agents async API | DevRev | Docs"
},
{
"id": "ART-2895_KNOWLEDGE_NODE-2",
"text": "view their past conversations. Identifying your users also enables more personalized engagement.\\n\\nIn this flow, you have to generate a session token for every user who visits your website. The session token identifies the customer when they interact with the widget. The session token is generated using the application access token and customer information. It should be generated on your website\\xe2\\x80\\x99s back end since the app token needs to be kept hidden.\\n\\nTo identify logged-in users,",
"title": "Identify your users with PLuG — DevRev | Docs"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-34",
"text": "minutes after a conversation is created.\\n* Any new message sent directly in the channel within this time frame is appended to the existing conversation.\\n* A new direct message from the customer resets the roll window timer.\\n* Any message sent from DevRev will be synced to the thread of the first message that initiated the conversation.\\n* Only messages within the thread of the originating message of the conversation are synced.\\n* Messages within Slack threads of follow-ups sent directly to",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-6174_KNOWLEDGE_NODE-27",
"text": "happens automatically:\\n\\n* The original conversation moves to *Archived* stage and cannot be reopened.\\n* A new ticket is created with:\\n + All internal discussions and customer messages copied from the conversation\\n + Equivalent metadata as the conversation, including source channel, customer account information, and external members added as **reported by** on the ticket\\n + An AI-generated ticket title and description based on customer messages\\n\\nConvert conversations to",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-1974_KNOWLEDGE_NODE-33",
"text": "have been addressed.\\n\\n A conversation set to *resolved* still shows in the end-user's widget. If they respond again, it reopens the conversation and set the status to *needs response*.\\n* *Archived*\\n\\n The final stage for conversation.\\n\\n[PreviousTicket-Team Performance](/docs/dashboards/ticket-team-performance)[NextConversation to ticket conversion](/docs/product/conversation-ticket)\\n\\n#### On this page\\n\\n* [Stages](#stages)\\n\\n[Enterprise grade security to protect customer",
"title": "Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-33",
"text": "DevRev app.\\n\\nIf a message is sent to a Slack thread belonging to an archived conversation, the Slack snap-in creates a new follow-up conversation, and all messages sync to this new conversation.\\n\\n![]()\\n\\nA Slack channel can be linked to only one DevRev account workspace, and vice versa.\\n\\nConversation roll window\\n------------------------\\n\\nTo avoid multiple conversations for related customer messages, a **conversation roll window** is used.\\n\\n* The roll window remains active for five",
"title": "Slack | Integrate | Snap-ins | DevRev"
}
] |
14cd4d8e-c6b6-4e4f-9b87-a463ebc9efe6
|
PLuG stops responding to clients when they send a photo
|
[
{
"id": "ART-17220_KNOWLEDGE_NODE-10",
"text": "|\\n```\\n\\nDelay response (for rate limiting)\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | await adapter.emit(ExtractorEventType.ExtractionAttachmentsDelay, { |\\n| 2 | delay: \"30\", // Delay in seconds |\\n| 3 | }); |\\n```\\n\\nError response\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | await adapter.emit(ExtractorEventType.ExtractionAttachmentsError, { |\\n| 2 | error: \"Informative error message\", |\\n| 3 | }); |\\n```\\n\\n##### \\n\\nThe snap-in must always emit exactly one response event.\\n\\nWas this page",
"title": "Attachments extraction | DevRev | Docs"
},
{
"id": "ART-17220_KNOWLEDGE_NODE-9",
"text": "console.warn(\\'Failed attachment metadata\\', item); |\\n| 22 | } |\\n| 23 | |\\n| 24 | return { |\\n| 25 | error: { |\\n| 26 | message: `Failed to fetch attachment ${id} from URL.`, |\\n| 27 | }, |\\n| 28 | }; |\\n| 29 | } |\\n| 30 | } |\\n```\\n\\nEmitting responses\\n------------------\\n\\nThe snap-in must send exactly one response to AirSync when extraction is complete:\\n\\nSuccess response\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | await adapter.emit(ExtractorEventType.ExtractionAttachmentsDone);",
"title": "Attachments extraction | DevRev | Docs"
}
] |
59e823a3-bae5-43c1-afc7-a244f05f02cd
|
workflow trigger ticket severity blocker
|
[
{
"id": "ART-1976_KNOWLEDGE_NODE-28",
"text": "scenarios\\n----------------------------\\n\\n* Ticket routing based on customer inquiry keywords.\\n* Group-specific routing based on customer account assignments.\\n* Assignment routing based on severity and subtype.\\n* Custom field and tag-based routing.\\n* First responder ticket assignment.\\n\\nSystem requirements\\n-------------------\\n\\n* Administrator privileges are required for workflow deployment and execution.\\n* User status (active/away) is configurable through the profile",
"title": "Routing | Computer for Support Teams | DevRev"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-506",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-506",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-507",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-506",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-505",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-507",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-463",
"text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-447",
"text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-452",
"text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-447",
"text": "organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-474",
"text": "organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-468",
"text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-455",
"text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-476",
"text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-476",
"text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-520",
"text": "severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided subtypes.\\n\\ntype enum Optional\\n\\nFilters for work of the provided types.\\n\\nAllowed values:",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-520",
"text": "severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided subtypes.\\n\\ntype enum Optional\\n\\nFilters for work of the provided types.\\n\\nAllowed values:",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-460",
"text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-520",
"text": "severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided subtypes.\\n\\ntype enum Optional\\n\\nFilters for work of the provided types.\\n\\nAllowed values:",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-519",
"text": "severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided subtypes.\\n\\ntype enum Optional\\n\\nFilters for work of the provided types.\\n\\nAllowed values:",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-2009_KNOWLEDGE_NODE-27",
"text": "ticket is closed or reopened.\\n* Post in the linked conversation when a ticket is linked.\\n* Post in child issue timeline when parent issue is closed.\\n* Post in parent issue timeline when child issue is closed.\\n* Post to issue's timeline when linked ticket's severity is changed.\\n* Post in ticket's timeline when an issue linked to it is closed.\\n* Post in enhancement's timeline when any linked issue is *In Development*.\\n* Update ticket's stage when linked issue's state changes.\\n* Update",
"title": "Convergence | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-452",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-447",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-452",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-449",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-446",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-447",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-450",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-447",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-449",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-446",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-448",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-452",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-446",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-455",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-448",
"text": "response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Get — DevRev | Docs"
}
] |
4ba07998-0726-46bb-b167-95ca5fecdf72
|
unable to add recipients or CC in email over ticket
|
[
{
"id": "ART-2027_KNOWLEDGE_NODE-30",
"text": "or @mentioned in the DevRev app.\\n\\n *Is able to:* View the ticket on the portal and reply via email as an email member.\\n* A customer admin for the same workspace\\n\\n *Added to:* **Customer Admins** group.\\n\\n *Is able to:* View the ticket on the portal once their workspace is updated on the ticket.\\n* An end user outside original sender's organization\\n\\n *Added to:* **To** or **CC** fields in the email thread, or mentioned in the DevRev app (adds them to **CC**).\\n\\n *Is able to:* Reply",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-40",
"text": "Description |\\n| --- | --- | --- |\\n| To/CC Field Management | To / Cc fields | Automatically assigns visibility permissions to added recipients. Warns if invalid users exist. |\\n| Text Formatting & Styling | Toolbar (bold, italics, etc.) | Apply rich text formatting including color highlights and custom styles. |\\n| Change Sender Email | Email icon (top-right) | Select a different From email address from configured options in Email snap-in. |\\n| Enhance Message with AI | Purple wand icon | Use",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-55",
"text": "test email to your configured address from the deliverability tool and confirm that a conversation or ticket is created.\\n2. Respond from the test conversation or ticket in DevRev to the address mentioned in the deliverability check tool.\\n\\nYou need to add the address as a contact, which can be done in the email composer page.\\n\\n1. Check the status of the email sent by coming back to the chosen tool.\\n\\nIf the **DMARC Compliance checks** on the tool pass, then DevRev email is",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-33",
"text": "members** does not remove them from the **Reported by** field.\\n\\nShadow users can also be subscribers and email members.\\n\\n* **CCed members in email**: The CCed members in emails will be added to reporters if they are contacts in the workspace to which the ticket belongs. They will be added to email members if they are part of the ongoing email thread, without any workspace restriction.\\n* **Shadow users**: Users created for tracking and record-keeping purposes that do not have access to the",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-36",
"text": "contact](https://docs.devrev.ai/product/plug) must be created first for any emails to be added as subscribers.\\n* **Needs response**: Set to true whenever a new customer message is received on the ticket to ensure that no customer messages are missed. If a particular customer message does not need a response, the **Needs response** toggle can be turned off by the user. Turning off the **Needs response** toggle does not affect the SLA metrics.\\n\\nThese attributes can be effectively used in",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-63",
"text": "support tickets on behalf of customers\\xe2\\x80\\x94without granting customers access to these tickets. This feature enables internal collaboration while keeping the ticket invisible to the customer until explicitly made external.\\n\\nEven if a ticket contains customer-related information (such as the customer workspace or the **Reported by** field), it remains inaccessible to the customer unless it is explicitly converted into an external ticket. The **Customer Messages** tab is unavailable for",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-32",
"text": "**Reported by** field, first choose the corresponding account and workspace in the **Customer** attribute. After this selection, the contact's name will appear in the **Reported by** list.\\n* **Email members**: Participants in the ongoing email thread, dependent on the last email. This attribute automatically updates based on the last email sent from or received on DevRev.\\n\\n![]()\\n\\nAdding members to **Email members** also adds them to the **Reported by** field. Removing members from **Email",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-16806_KNOWLEDGE_NODE-27",
"text": "Internal Ticket** from the **Ticket Creation** dropdown.\\n* **Focused UI:** The **Customer Messages** tab is disabled on internal tickets to prevent unintended communication.\\n\\nThis feature supports internal workflows while giving you control over when customer engagement begins.\\n\\n![]()\\xc2\\xa0For more information about *Conversation and Ticket Workflows*, refer to the following articles: \\xe2\\x80\\xa3 [Auto parts to conversation | Automate | Snap-ins](/docs/automations/auto-parts)",
"title": "July 2025 | Changelog | DevRev"
}
] |
19d771bc-215b-4d0a-9a72-2d3da44804b5
|
migration of Tickets Issues Incidents from acme to spd instance preserving original work ID numbers and timestamps
|
[
{
"id": "ART-997_KNOWLEDGE_NODE-26",
"text": "is built upon the core tenancy keys (e.g. dev_org), we have a ton of flexibility, clarity and overlap avoidance.\\n\\nFor example, look at the following 2 IDs from the above examples:\\n\\n\\n don:core:dvrv-us-1:**devo/55**:issues/789\\n don:core:dvrv-us-1:**devo/44**:issues/789\\n\\n\\nThese are issues from 2 different orgs, they have the same issue ID, but because of the devo in the DON they are both globally unique. This allows us to keep the type ids clean but still maintain a globally unique ID",
"title": "How to Write an Object Model That Doesn't Suck"
}
] |
8e4d51df-6adc-4047-9c0d-30ec56e13fc6
|
Knowledge article generation from single cases or case clusters
|
[
{
"id": "ART-1983_KNOWLEDGE_NODE-29",
"text": "on\\xe2\\x80\\x94it learns. It autonomously generates new Q&As based on the resolved conversation, marking them for review under the *Review Needed* status.\\n\\nA Q&A isn't created if it is similar to the existing Q&A to avoid duplication.\\n\\n```\\nSatisfactory answer\\n\\n\\n\\nSimilar Q&A found\\n\\n\\n\\nNo answer or \\ntalk to engineer\\n\\n\\n\\nImproves Turing\\n\\n\\n\\nCustomer query\\n\\n\\n\\nTuring\\n\\n\\n\\nConversation \\nresolved\\n\\n\\n\\nNo new Q&As \\ncreated\\n\\n\\n\\nQ&As created\\n```\\n\\nTo enable automatic",
"title": "Questions & answers | Computer for Support Teams | DevRev"
}
] |
db5bd216-2f02-42a4-a79a-371d88624178
|
parts when creating an issue
|
[
{
"id": "ART-1992_KNOWLEDGE_NODE-26",
"text": "importance of the issue. Priorities can be set to P0, P1, P2, and P3. P0 is the highest priority and P3 is the lowest.\\n* **Stage**: The current state of the issue. The stage attribute is used to track the progress of the issue through its lifecycle. For more information on stages, see [stages](#stages).\\n* **Part**: The part of the company or product that the issue is related to. For more information on parts, see [parts](./parts).\\n* **Created by**: The person who created the issue.\\n*",
"title": "Issues | Computer for Builders | DevRev"
},
{
"id": "ART-1992_KNOWLEDGE_NODE-31",
"text": "on the top right corner of your screen.\\n3. Add a title and description for your new issue. You can also attach files related to the issue in the description.\\n4. Select which part of the company/product this issue is related to.\\n\\n ![]()\\n5. Enter other attributes for the issue: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the issue; select the workspace that the issue pertains to.\\n6. If there are",
"title": "Issues | Computer for Builders | DevRev"
},
{
"id": "ART-1002_KNOWLEDGE_NODE-1",
"text": "\\xe2\\x86\\x92 Issues\\n Items to track customer requests/problems \\xe2\\x86\\x92 Tickets\\n\\n\\nGiven the converged nature of the DevRev platform, we have both Tickets, and Issues, so when do you use what? The answer is \\xe2\\x80\\x9cit depends\\xe2\\x80\\x9d on what your role is on the part you\\xe2\\x80\\x99re creating the work item on. In general, issues should be restricted to those individuals that either own or contribute to a part. Tickets should be used for all customer/consumer (internal or",
"title": "Tickets, Issues: When to Use Each"
},
{
"id": "ART-1950_KNOWLEDGE_NODE-46",
"text": "or bug fix to include it in the release notes.\\n* **Customer impact**: The impact of the part on the customer.\\n* **Target close date**: The date by which the part is expected to be resolved.\\n* **Target start date**: The date by which the part is expected to start.\\n\\nYou can add custom attributes to issues to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\nSubtypes\\n--------\\n\\nYou can create subtypes of issues to",
"title": "Parts & trails | Computer by DevRev | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-29",
"text": "**Severity**: The importance of the ticket. Severity can be set to low, medium, blocker, or high.\\n* **Stage**: The current state of the issue. The stage attribute is used to track the progress of the issue through its lifecycle. For more information on stages, see [stages](#stages).\\n* **Part**: The part of the company or product that the issue is related to. For more information on parts, see [parts](./parts).\\n* **Created by**: The user who created the ticket.\\n* **Created date**: The date",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1002_KNOWLEDGE_NODE-2",
"text": "external) items.\\n\\nThe following figure shows a decision tree that will help you identify what work type you should be using (this is not global but part specific):\\n\\n\\n\\nFor example, if I work on part foo, I can create issues on it. However, if I am a consumer of part bar I would create tickets which would then be triaged and potentially escalated into an issue by that team.\\n\\nWhy\\n\\n\\n Noise and context switching kill productivity\\n\\n\\nHistorically, a huge pain point has been that any",
"title": "Tickets, Issues: When to Use Each"
},
{
"id": "ART-8441_KNOWLEDGE_NODE-36",
"text": "off if you choose to explicitly create issues and link your GitLab activity or you can enable it either for PR creation or branch creation event.\\n* Select the default part under **Default part for autonomous issues** as a default Part ID if you enable **Track autonomous work**. Autonomous issues originating from GitLab are attributed to a default part. You can configure the default part while setting up your snap-in. Every issue in DevRev must have a part attribution.\\n\\n### Autonomous work",
"title": "GitLab | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2030_KNOWLEDGE_NODE-37",
"text": "disabled if you choose to explicitly create issues and link your Bitbucket activity or you can enable it either for PR creation or branch creation event.\\n* Select the default part under **Default part for autonomous issues** as a default Part ID if you enable **Track autonomous work**. Autonomous issues originating from BitBucket will be attributed to a default part. You can configure the default part while setting up your snap-in. Every issue in DevRev must have a part attribution.\\n\\n###",
"title": "Bitbucket | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1947_KNOWLEDGE_NODE-33",
"text": "language is reflected in issues.\\n\\nIssues\\n------\\n\\nLater on, a software engineer may start work on this ticket by creating an issue and breaking that issue into smaller pieces with tasks. An issue describes what the developer will work on and is created or accepted by someone who owns or works on the associated part of the product. This distinction allows developers to break up a ticket from an external user into issues as they see fit and delegate the work to other team members as",
"title": "Apps | Computer by DevRev | DevRev"
},
{
"id": "ART-1992_KNOWLEDGE_NODE-28",
"text": "various vistas in DevRev to track specific work, capacity, and more.\\n\\nYou can add custom attributes to issues to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\nIssues are attached to parts in order to align efforts with product priorities.\\n\\nAs to the size of an issue and the flexibility it offers to manage changes in size, issues offer hierarchy in the form of parent-child relationships and granularity.\\n\\nFrom",
"title": "Issues | Computer for Builders | DevRev"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-31",
"text": "needed. For example, if the ticket is found to be spam, you can automatically add a comment to the ticket.\\n\\n**Suggest part**\\n\\nOften, your integrations create tickets or issues associated with a default part. The suggest part takes the ID of a ticket or issue and suggests a relevant part. You can use this to route your tickets or issues to the most appropriate part of the product. For example, when a ticket is created, you can find a relevant part and update the ticket with the suggested",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-439",
"text": "https://api.devrev.ai/works.create \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"type\": \"issue\", > \"applies_to_part\": \"string\", > \"owned_by\": [ > \"string\" > ], > \"title\": \"string\" > } \\'\\n200 Successful 1 { 2 \" work \" : { 3 \" type \" : \" issue \" , 4 \" actual_start_date \" : \" 2023-01-01T00:00:00Z \" , 5 \" developed_with \" : [ 6 { 7 \" type \" : \" capability \" , 8 \" name \" : \" string \" , 9 \" owned_by \" : [ 10 { 11 \" type \" : \" dev_user \" , 12 \"",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1994_KNOWLEDGE_NODE-33",
"text": "sprint board and click **+Issue**.\\n Create a new issue, assign it to the part, sprint and add the owner.\\n\\n ![]()\\n\\n Sprints are not coordinated with stages.\\n3. Select issues that you would like to assign to **Sprint 1** or **Sprint 2** then click **Move** in the toolbar at the top of the screen and select the sprint.\\n\\n ![]()\\n4. Go to **Sprint 1** or **Sprint 2** to see that issues are displayed.\\n\\n ![]()\\n\\n The sprint is also displayed in (and can be changed from) the",
"title": "Sprint mode | Computer for Builders | DevRev"
},
{
"id": "ART-1957_KNOWLEDGE_NODE-31",
"text": "can select a date in this field. For example, \"Date of bug identified: 19/07/2024\".\\n + **Part**: Select the part to which this object belongs. It could be an enhancement, feature, capability, runnable, linkable, or product.\\n + **Dev user**: Select one or multiple users from the dropdown.\\n + **Customer**: Assign the object to an existing customer workspace.\\n + **Account**: Assign the object to a customer account.\\n + **Workspace**: Assign the object to a workspace.\\n\\n",
"title": "Object customization | Computer by DevRev | DevRev"
},
{
"id": "ART-1275_KNOWLEDGE_NODE-18",
"text": "= `Ticket created at ${date.toLocaleString()}`; |\\n| 14 | const ticketBody = `This ticket was created by a snap-in at ${date.toLocaleString()}`; |\\n| 15 | |\\n| 16 | const response = await devrevSDK.worksCreate({ |\\n| 17 | title: ticketName, |\\n| 18 | body: ticketBody, |\\n| 19 | // The ticket is created in the PROD-1 part. Rename this to match your part. |\\n| 20 | applies_to_part: \"PROD-1\", |\\n| 21 | // The ticket is owned by the DEVU-1 user. Rename this to match the required user. |\\n| 22 |",
"title": "Using a snap-in to perform a DevRev action | DevRev | Docs"
},
{
"id": "ART-1483_KNOWLEDGE_NODE-21",
"text": "devrevSDK.worksCreate({ \\n 17| title: ticketName, \\n 18| body: ticketBody, \\n 19| // The ticket is created in the PROD-1 part. Rename this to match your part. \\n 20| applies_to_part: \"PROD-1\", \\n 21| // The ticket is owned by the DEVU-1 user. Rename this to match the required user. \\n 22| owned_by: [\"DEVU-1\"], \\n 23| type: publicSDK.WorkType.Ticket, \\n 24| }); \\n 25| \\n 26| console.log(response); \\n",
"title": "Using a snap-in to perform a DevRev action — DevRev | Docs"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-38",
"text": "the top-right corner of your screen.\\n3. Add a title and description for your new ticket. You can also attach files related to the ticket in the description.\\n4. Select which part of the company/product this ticket is related to.\\n\\n ![]()\\n5. Enter other attributes for the ticket: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the ticket; select the workspace that the ticket pertains to.\\n6. If there are",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-15989_KNOWLEDGE_NODE-24",
"text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Automated part update](/docs/automations/automated-part-update)\\n\\nAutomated part update\\n=====================\\n\\nThe Automated part update snap-in streamlines the updating of issue or ticket parts based on the initial part and target field defined in its configuration. It monitors the creation events of issues and tickets, ensuring that new entries match the part specified in the **Initial Part of Issue/Ticket** input field. Upon",
"title": "Automated part update | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1950_KNOWLEDGE_NODE-25",
"text": "be recursively made of smaller parts. Events and work items must be related to parts. In general, parts are the core objects that almost all other objects are linked to, which helps enforce the notion of tying everything back to the product or service.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Trails\\n\\n*Trails* is an extensible interface that allows you to view and manage your part hierarchy and related items. Think of it like a graph canvas that\\'s rendering linkages among items\\xe2\\x80\\x94including",
"title": "Parts & trails | Computer by DevRev | DevRev"
},
{
"id": "ART-17231_KNOWLEDGE_NODE-102",
"text": "to which the issue belongs. |\\n| `stage` | enum | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Stage of the object |\\n| `tags` | reference (collection)\\xe2\\x86\\x92[#record:tag] | | Tags associated with the object |\\n| `target_close_date` | timestamp | | Timestamp when the work is expected to be complete |\\n| `target_start_date` | timestamp | | Target start date for the object |\\n| `title` | text | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Title of the work object |\\n\\n#### Enum values\\n\\n**priority**\\n\\n| Value | Name |",
"title": "Supported DevRev object types | DevRev | Docs"
},
{
"id": "ART-17231_KNOWLEDGE_NODE-99",
"text": "User ID of the user that created the object |\\n| `estimated_effort` | float | | Estimated effort to complete the issue |\\n| `fallback_parts` | reference\\xe2\\x86\\x92[#category:part] | | Other values that could serve as part if apples\\\\_to\\\\_part\\\\_id is found to be invalid. |\\n| `item_url_field` | text | | Link to the item in the origin system |\\n| `modified_by_id` | reference\\xe2\\x86\\x92[#category:user] | | User ID of the user that last modified the object |\\n| `owned_by_ids` | reference",
"title": "Supported DevRev object types | DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-437",
"text": "object.\\nIssue Show 19 properties\\nOR\\nOpportunity Show 21 properties\\nOR\\nTask Show 17 properties\\nOR\\nTicket Show 21 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nwork object\\nShow 4 variants\\nPOST / works.create\\ncURL\\n$ curl -X POST https://api.devrev.ai/works.create \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"type\": \"issue\", > \"applies_to_part\": \"string\", > \"owned_by\": [ > \"string\" > ], > \"title\": \"string\" > } \\'\\n200",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-2010_KNOWLEDGE_NODE-25",
"text": "from a CSV file. The CSV file supports the following columns:\\n\\n```\\n```\\n1 Title,Description,Owners,Part,Tags,Subtype,WorkType\\n\\n\\n\\n2 Front page not loading,\"This is a sample ticket body with \\xe2\\x80\\x9c\\xe2\\x80\\x9d quotes\",[email protected],PROD-1,frontend,subtype1,Ticket\\n\\n\\n\\n3 APIs returning errors,\"The user.get API is returning 500\",[email protected],PROD-2,backend,subtype2,Issue\\n```\\n```\\n\\nThe Title column is required, while the others are optional. If the WorkType column",
"title": "Bulk work item uploader | Automate | Snap-ins | DevRev"
}
] |
74ba3430-6056-4c36-b1c2-45ccabb540fa
|
filtering by custom fields in conversation views
|
[
{
"id": "ART-1512_KNOWLEDGE_NODE-1",
"text": "then iteration starts from the beginning.\\n\\ncustom_fieldsmap from strings to anyOptional\\n\\nFilters for custom fields.\\n\\ngroupstringOptional\\n\\nFilters for conversation that belong to the given groups.\\n\\nis_creator_verifiedbooleanOptional\\n\\nFilters for conversations that are created by verified users.\\n\\nis_spambooleanOptional\\n\\nFilters for conversations that are spam.\\n\\nlimitintegerOptional\\n\\nThe maximum number of conversations to return. The default is",
"title": "List Conversations (Beta) — DevRev | Docs"
}
] |
fc419974-3881-40f8-a8ca-a899d411f735
|
Global CDN support for optimal performance worldwide
|
[
{
"id": "ART-992_KNOWLEDGE_NODE-10",
"text": "to k.sni.global.fastly.net instead of your web servers. This means when resolving foo.bar.com it would direct the traffic to hit Fastly\\xe2\\x80\\x99s servers.\\n\\nThis is important for a few key reasons, it enables them to hit a local Fastly point-of-presence (POP) and also allows them to be able to handle DDoS attacks before they hit your origin (if configured correctly, as I will cover).\\n\\nHere you can see an example CNAME resolving to Fastly:\\n\\n; <<>> DiG 9.16.1-Ubuntu <<>> foo.bar.com\\n;;",
"title": "Perimeter security with Fastly edge and AWS — Part I"
},
{
"id": "ART-992_KNOWLEDGE_NODE-13",
"text": "delivery model where we can offload the burden of requests from hitting origin and push more to the edge (more to come here!).\\n\\nIn our case we are using a mix of edge compute (C@E) which allows us to compile and execute RUST code on Fastly\\xe2\\x80\\x99s edge, which can also take advantage of their CDN which can cache content from origin.\\n\\nA quick note on WebAssembly (WASM)\\xe2\\x80\\xa6 this is one thing that is very interesting/exciting and will be one of the core enablers to making clients",
"title": "Perimeter security with Fastly edge and AWS — Part I"
},
{
"id": "ART-12476_KNOWLEDGE_NODE-2",
"text": "access control using DevRev\\xe2\\x80\\x99s Multi-factor Authorization (MFA) system.\\n\\nImproved reliability\\n\\nA platform powered by a team you can count on\\n\\nOmni-channel support: Access our new PLuG widget offering proactive HyperCare support with single-touch deflection across multiple capabilities\\n\\nReal-time updates: Receive live updates on your tickets and track development progress transparently\\n\\nReliable SDK Delivery with Fastly CDN: PLuG SDK is delivered via Fastly CDN which ensures",
"title": "The Future of Sessions - Powered By DevRev"
}
] |
567e8718-9e24-4916-a134-f4756b25a74f
|
ticket portal confirmation message sent to user immediately
|
[
{
"id": "ART-2912_KNOWLEDGE_NODE-24",
"text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Ticket email notifier](/docs/automations/ticket-email-notifier)\\n\\nTicket email notifier\\n=====================\\n\\nThe Ticket Email Notifier snap-in automates email notifications for specific ticket subtypes. When a ticket of the chosen subtype is created, it generates and sends a customized email.\\n\\n![]()\\n\\nFor more information, refer to the [Ticket email notifier snap-in](https://marketplace.devrev.ai/ticket-email-notifier) on the",
"title": "Ticket email notifier | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1953_KNOWLEDGE_NODE-33",
"text": "[[email protected]](mailto:[email protected])\\n* **Subject**: \"CSAT for TKT-XXX\"\\n\\n![]()\\n\\nThis email is only sent to organizations that have installed [CSAT snap-in](https://docs.devrev.ai/automations/csat-conv).\\n\\nAuto customer reply\\n-------------------\\n\\n* **Trigger**: A new conversation is initiated from a customer.\\n* **Action**: An automated reply is sent.\\n* **Sender**: {Company\\\\_Name} [[email protected]](mailto:[email protected])\\n* **Subject**: \"<customer email",
"title": "Customer email notifications | Computer by DevRev | DevRev"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-36",
"text": "\\xe2\\x80\\x9cWe have received your request for help with the following: \\n{{Ask AI > Output > Output string}}. \\nA support agent will review the request and respond within your organization's SLA.\\xe2\\x80\\x9d\\n\\n\\n\\nAsk AI\\n\\n\\n\\nPrompt: \\xe2\\x80\\x9cSummarize the ticket based on \\n{{Ticket Created > Output > Description}}, \\n{{Ticket Created > Output > Title}}, \\n{{Ticket Created > Output > Applies to Part > Name}}, and",
"title": "Workflows | Computer by DevRev | DevRev"
}
] |
722fb588-1b64-4b74-95fd-3ce55ccf6d61
|
Data isolation ensuring customers only see their own data
|
[
{
"id": "ART-738_KNOWLEDGE_NODE-14",
"text": "Rather than physically segmenting tenant data, we built tenancy into the objects using specific attributes which act as partitions\\n This allows us to create macro partitions (e.g., customer) or extremely granular partitions (e.g., user level)\\n This gives us a ton of flexibility as all data is in one place and the granularity can range from macro to micro\\n \\n \\n We designed our services for the cloud\\n \\n Being built in the \\xe2\\x80\\x9cera of cloud\\xe2\\x80\\x9d we had a",
"title": "DevRev | Built for AI (not by AI... yet)"
},
{
"id": "ART-997_KNOWLEDGE_NODE-20",
"text": "tenancy key unique to each tenant (dev_org and rev_org). Using this, we have built-in safeguards to ensure only actors from a certain tenant can access objects of that tenant. Our authorization, mongo-client and other services all leverage this tenancy key and use this for validations.\\n\\nEven if there is a case for physical segmentation, it could still leverage this attribute to define which physical partition it goes to.\\n\\nRemember, you don\\xe2\\x80\\x99t know what you don\\xe2\\x80\\x99t know,",
"title": "How to Write an Object Model That Doesn't Suck"
},
{
"id": "ART-997_KNOWLEDGE_NODE-19",
"text": "There is a time and place for physical separation of data, however, this isn\\xe2\\x80\\x99t always required and logical tenancy will do in most cases. Even if you don\\xe2\\x80\\x99t initially plan for multi-tenancy or need it, it\\xe2\\x80\\x99s never a bad idea to plan ahead for this.\\n\\nRather than partitioning tenant data as the storage layer, which was very inefficient, we built multi-tenancy into every one of our objects. All objects inherit from the root base class (Atom), which includes a",
"title": "How to Write an Object Model That Doesn't Suck"
},
{
"id": "ART-12476_KNOWLEDGE_NODE-1",
"text": "designed to meet GDPR and SOC 2 compliance requirements, with controls in place to support your data privacy needs.\\n\\nAdvanced enterprise login: Seamless SAML compliance for all enterprise logins regardless of your SSO provider.\\n\\nRegional data residency options: We offer data residency options in Europe, Australia, US East (Virginia), and India, with logical data isolation and access control features.\\n\\nSelf-serve user management: Easily add or remove users from your workspace and manage",
"title": "The Future of Sessions - Powered By DevRev"
},
{
"id": "ART-970_KNOWLEDGE_NODE-92",
"text": "built multi-tenancy into the object\\n \\n Rather than physically segmenting tenant data, we built tenancy into the objects using specific attributes which act as partitions\\n This allows us to create macro partitions (e.g., customer) or extremely granular partitions (e.g., user level)\\n This gives us a ton of flexibility as all data is in one place and the granularity can range from macro to micro\\n \\n \\n We designed our services for the cloud\\n \\n Being built in",
"title": "The Story"
},
{
"id": "ART-970_KNOWLEDGE_NODE-102",
"text": "groundwork, ensuring we possessed the requisite keys to partition and segment data effectively. This profound understanding of the structure empowered us to fashion granular and precise authorization mechanisms. By dedicating upfront effort to this aspect, we\\xe2\\x80\\x99ve endowed our system with authorization capabilities that some mature companies can only envision, including support for role-based access control (RBAC), attribute-based access control (ABAC), policy-based access control",
"title": "The Story"
},
{
"id": "ART-16789_KNOWLEDGE_NODE-4",
"text": "insights across previously siloed information.Q: How does Computer handle data privacy and security?\\n\\nAlternative questions: \"Is my data safe?\" \"Data security with Computer\" \"Access controls in Computer\"\\n\\nAnswer: Computer preserves all your existing permissions and access controls. People only see information they\\'re supposed to have access to. We\\'re SOC 2 compliant, GDPR ready, and maintain individual-level access controls for personal data like calendars and emails.About ComputerQ: What",
"title": "Computer General FAQs"
},
{
"id": "ART-970_KNOWLEDGE_NODE-103",
"text": "(PBAC), field-level security, lease-based access, conditional policies, and more.\\n\\nFrom a compliance perspective, our rigorous efforts encompassed adherence to regulations such as SOC2 and ISO-27001. These considerations exerted influence over various facets of our architecture, notably shaping our approach to edge security through our web-application firewall (WAF) and our handling of configuration management.\\n\\nEven within our internal operations, we wholeheartedly embraced the zero-trust",
"title": "The Story"
},
{
"id": "ART-1958_KNOWLEDGE_NODE-30",
"text": "do not, by default, have permission to read any datasets besides their own. Admins are responsible for granting read permissions to all or a subset of datasets, which platform users can then utilize in building dashboards or reports.\\n\\n### Sharing\\n\\nThe share functionality allows dashboard or report editors to grant read or update permissions to other users.\\n\\n1. Select **Share** from the actions drop-down.\\n2. Search for the desired user, assign them a role (Editor or Viewer), then click",
"title": "Access control | Computer by DevRev | DevRev"
},
{
"id": "ART-738_KNOWLEDGE_NODE-13",
"text": "customization in from the start\\n \\n We knew extensibility would be key for any platform\\n Given the simplicity of customization, we can easily extend our object model with new annotations or context that can be used and fed into models\\n This means, that a customer or vendor, can easily extend our object model with new data on objects which can be used by models, new object types, or with the output of a model\\n \\n \\n We built multi-tenancy into the object\\n \\n",
"title": "DevRev | Built for AI (not by AI... yet)"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-32",
"text": "on the following URL: support.devrev.ai/<yourcompany>.\\n* Your customers can log in on the portal by entering their registered email address and OTP sent to that email address.\\n\\n![]()\\n\\n### Customer roles and permissions\\n\\nThe customer portal has two levels of customer roles and permissions:\\n\\n* **Verified customers**: Customers who can log in on the portal and see the tickets that they have created.\\n* **Customer admins**: Customers who can log in on the portal and see not just their own",
"title": "Customer portal | Computer for Support Teams | DevRev"
}
] |
e1a58e97-0e67-4f57-997d-3ef109d75a22
|
API to fetch or manage knowledge base content
|
[
{
"id": "ART-1507_KNOWLEDGE_NODE-5",
"text": "https://api.devrev.ai/articles.list \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{}\\'\\n[/code] \\n \\nTry it\\n\\n200Successful\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"articles\": [ \\n 3| { \\n 4| \"applies_to_parts\": [ \\n 5| { \\n 6| \"type\": \"product\", \\n 7| \"id\": \"applies_to_parts\", \\n 8| \"name\": \"applies_to_parts\", \\n",
"title": "List Articles (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-15291_KNOWLEDGE_NODE-0",
"text": "b'Get Article (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nGet Article (POST)\\n==================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.get\\n\\nPOST\\n\\n/articles.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/articles.get \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Get Article (POST) | DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-36",
"text": "api.devrev.ai / articles.get\\nGets an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles List Articles.\\n\\nGET https:// api.devrev.ai / articles.list\\nLists a collection of articles.\\nQuery parameters.\\n\\napplies_to_parts string Optional\\nFilters for articles belonging to any of the provided parts.\\narticle_type \"article\" or",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-15294_KNOWLEDGE_NODE-0",
"text": "b'Get Article | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nGet Article\\n===========\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/articles.get\\n\\nGET\\n\\n/articles.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -G https://api.devrev.ai/articles.get \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -d id=ARTICLE-12345 |\\n```\\n\\n[Try",
"title": "Get Article | DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-35",
"text": "Post.\\n\\nPOST https:// api.devrev.ai / articles.get\\nGets an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles List Articles.\\n\\nGET https:// api.devrev.ai / articles.list\\nLists a collection of articles.\\nQuery parameters.\\n\\napplies_to_parts string Optional\\nFilters for articles belonging to any of the provided",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1504_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/articles/get-article-post)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[articles](/beta/api-reference/articles/count)\\n\\n# Get Article (POST)\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.get\\n\\nTry it\\n\\nGets an article.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired\\n\\nThe ID of the required article.\\n\\n### Response\\n\\nGet article response.\\n\\narticleobject\\n\\nShow 20 properties\\n\\nPOST\\n\\n/articles.get\\n\\ncURL\\n\\n[code]\\n\\n $|",
"title": "Get Article (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-1316_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/articles/get-article)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[articles](/beta/api-reference/articles/count)\\n\\n# Get Article\\n\\nGET\\n\\nhttps://api.devrev.ai/articles.get\\n\\nTry it\\n\\nGets an article.\\n\\n### Query parameters\\n\\nidstringRequired\\n\\nThe ID of the required article.\\n\\n### Response\\n\\nGet article response.\\n\\narticleobject\\n\\nShow 20 properties\\n\\nGET\\n\\n/articles.get\\n\\n[code]\\n\\n $| curl -G https://api.devrev.ai/articles.get \\\\",
"title": "Get Article (Beta) — DevRev | Docs"
},
{
"id": "ART-1504_KNOWLEDGE_NODE-1",
"text": "curl -X POST https://api.devrev.ai/articles.get \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"ARTICLE-12345\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200Successful\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"article\": { \\n 3| \"applies_to_parts\": [ \\n 4| { \\n 5| \"type\": \"product\", \\n 6| \"id\": \"applies_to_parts\", \\n 7|",
"title": "Get Article (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-4069_KNOWLEDGE_NODE-0",
"text": "b'[](/public/api-reference/articles/list-articles-post)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Articles](/public/api-reference/articles/create-article)\\n\\n# List Articles (POST)\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.list\\n\\nTry it\\n\\nLists a collection of articles.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\napplies_to_partslist of stringsOptional\\n\\nFilters for articles belonging to any of the provided parts.\\n\\narticle_typelist of",
"title": "List Articles (POST) — DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-378",
"text": "https://api.devrev.ai / question-answers.get\\n\\nGets a question-answer.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nThe ID of the required question-answer.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nquestion_answer object\\nShow 12 properties\\nAPI Reference question-answers List Question Answers.\\n\\nGET https://api.devrev.ai / question-answers.list\\n\\nLists a collection of question-answers.\\n\\nQuery parameters.\\n\\napplies_to_articles string Optional\\n\\nFilters",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-380",
"text": "https://api.devrev.ai / question-answers.get\\n\\nGets a question-answer.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nThe ID of the required question-answer.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nquestion_answer object\\nShow 12 properties\\nAPI Reference question-answers List Question Answers.\\n\\nGET https://api.devrev.ai / question-answers.list\\n\\nLists a collection of question-answers.\\n\\nQuery parameters.\\n\\napplies_to_articles string Optional\\n\\nFilters",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-15295_KNOWLEDGE_NODE-0",
"text": "b'List Articles | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nList Articles\\n=============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/articles.list\\n\\nGET\\n\\n/articles.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/articles.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" |\\n```\\n\\n[Try",
"title": "List Articles | DevRev | Docs"
},
{
"id": "ART-1582_KNOWLEDGE_NODE-1",
"text": "\\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -d id=id |\\n```\\n\\n[Try it](/beta/api-reference/question-answers/get-question-answer?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"question_answer\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"answer\": \"string\", |\\n| 5 | \"applies_to_parts\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"name\": \"string\", |\\n| 10 | \"owned_by\": [ |\\n| 11 | { |\\n| 12 | \"display_id\": \"string\",",
"title": "Get Question Answer | DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-34",
"text": "endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Delete Article.\\n\\nPOST https:// api.devrev.ai / articles.delete\\nDeletes an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the article to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference articles Get Article.\\n\\nGET https:// api.devrev.ai / articles.get\\nGets an article.\\nQuery parameters.\\n\\nid string Required\\nThe ID of the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-15293_KNOWLEDGE_NODE-0",
"text": "b'List Articles (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nList Articles (POST)\\n====================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.list\\n\\nPOST\\n\\n/articles.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/articles.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > |",
"title": "List Articles (POST) | DevRev | Docs"
},
{
"id": "ART-4070_KNOWLEDGE_NODE-0",
"text": "b'[](/public/api-reference/articles/update-article)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Articles](/public/api-reference/articles/create-article)\\n\\n# Update Article\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.update\\n\\nTry it\\n\\nUpdates an article.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired`format: \"id\"`\\n\\nThe article\\xe2\\x80\\x99s ID.\\n\\naccess_levelenumOptional\\n\\nAllowed values:",
"title": "Update Article — DevRev | Docs"
},
{
"id": "ART-1500_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/articles/update-article)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[articles](/beta/api-reference/articles/count)\\n\\n# Update Article\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.update\\n\\nTry it\\n\\nUpdates an article.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired\\n\\nThe article\\xe2\\x80\\x99s ID.\\n\\naccess_levelenumOptional\\n\\nAllowed values: externalinternalprivatepublicrestricted\\n\\naliasesobjectOptional\\n\\nShow",
"title": "Update Article (Beta) — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1315_KNOWLEDGE_NODE-1",
"text": "-X POST https://api.devrev.ai/articles.delete \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"ARTICLE-12345\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200Successful\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"key\": \"value\" \\n 3| }\\n[/code] \\n \\n[Get ArticleUp Next](/beta/api-reference/articles/get-article)\\n\\n[Built",
"title": "Delete Article (Beta) — DevRev | Docs"
},
{
"id": "ART-1643_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-15292_KNOWLEDGE_NODE-0",
"text": "b'Create Article | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nCreate Article\\n==============\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.create\\n\\nPOST\\n\\n/articles.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/articles.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Create Article | DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-35",
"text": "required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Get Article Post.\\n\\nPOST https:// api.devrev.ai / articles.get\\nGets an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles List Articles.\\n\\nGET https:// api.devrev.ai / articles.list\\nLists a collection of",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-15297_KNOWLEDGE_NODE-0",
"text": "b'Update Article | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nUpdate Article\\n==============\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.update\\n\\nPOST\\n\\n/articles.update\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/articles.update \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Update Article | DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1601_KNOWLEDGE_NODE-1",
"text": "https://api.devrev.ai/question-answers.get \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/question-answers/get-question-answer-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"question_answer\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"answer\": \"string\", |\\n| 5 | \"applies_to_parts\": [ |\\n| 6 | { |\\n| 7 | \"display_id\":",
"title": "Get Question Answer (POST) | DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1507_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/articles/list-articles-post)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[articles](/beta/api-reference/articles/count)\\n\\n# List Articles (POST)\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.list\\n\\nTry it\\n\\nLists a collection of articles.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\napplies_to_partslist of stringsOptional\\n\\nFilters for articles belonging to any of the provided parts.\\n\\narticle_typelist of enumsOptional\\n\\nAllowed values:",
"title": "List Articles (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1789_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1314_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/articles/create-article)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[articles](/beta/api-reference/articles/count)\\n\\n# Create Article\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.create\\n\\nTry it\\n\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\n\\n### Request\\n\\nThis endpoint expects an",
"title": "Create Article (Beta) — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1584_KNOWLEDGE_NODE-1",
"text": "https://api.devrev.ai/question-answers.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" |\\n```\\n\\n[Try it](/beta/api-reference/question-answers/list-question-answers?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"question_answers\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"answer\": \"string\", |\\n| 6 | \"applies_to_parts\": [ |\\n| 7 | { |\\n| 8 | \"display_id\": \"string\", |\\n| 9 | \"id\": \"string\", |\\n| 10 | \"name\": \"string\", |\\n| 11 | \"owned_by\": [ |\\n| 12 | {",
"title": "List Question Answers | DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-37",
"text": "object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Delete Article.\\n\\nPOST https:// api.devrev.ai / articles.delete\\nDeletes an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the article to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference articles Get Article.\\n\\nGET https:// api.devrev.ai / articles.get\\nGets an article.\\nQuery parameters.\\n\\nid string Required\\nThe ID of the required",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-15293_KNOWLEDGE_NODE-1",
"text": "-H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/articles/list-articles-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"articles\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"owned_by\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"display_name\": \"string\", |\\n| 10 | \"display_picture\": { |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"id\": \"string\", |\\n| 13 | \"file\": { |\\n| 14 |",
"title": "List Articles (POST) | DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-37",
"text": "object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Delete Article.\\n\\nPOST https:// api.devrev.ai / articles.delete\\nDeletes an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the article to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference articles Get Article.\\n\\nGET https:// api.devrev.ai / articles.get\\nGets an article.\\nQuery parameters.\\n\\nid string Required\\nThe ID of the required",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1582_KNOWLEDGE_NODE-0",
"text": "b'Get Question Answer | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[question-answers](/beta/api-reference/question-answers/create-question-answer)\\n\\nGet Question Answer\\n===================\\n\\nBeta\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/question-answers.get\\n\\nGET\\n\\n/question-answers.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -G https://api.devrev.ai/question-answers.get",
"title": "Get Question Answer | DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-38",
"text": "article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Get Article Post.\\n\\nPOST https:// api.devrev.ai / articles.get\\nGets an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles List Articles.\\n\\nGET https:// api.devrev.ai / articles.list\\nLists a collection of",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-38",
"text": "article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Get Article Post.\\n\\nPOST https:// api.devrev.ai / articles.get\\nGets an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles List Articles.\\n\\nGET https:// api.devrev.ai / articles.list\\nLists a collection of",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-15291_KNOWLEDGE_NODE-1",
"text": "\"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"ARTICLE-12345\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/articles/get-article-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"article\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"owned_by\": [ |\\n| 5 | { |\\n| 6 | \"display_id\": \"string\", |\\n| 7 | \"id\": \"string\", |\\n| 8 | \"display_name\": \"string\", |\\n| 9 | \"display_picture\": { |\\n| 10 | \"display_id\": \"string\", |\\n| 11 | \"id\": \"string\", |\\n| 12",
"title": "Get Article (POST) | DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-4070_KNOWLEDGE_NODE-6",
"text": "https://api.devrev.ai/articles.update \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"ARTICLE-12345\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200articlesUpdateArticleExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"article\": { \\n 3| \"id\": \"foo\", \\n 4| \"owned_by\": [ \\n 5| { \\n 6| \"display_id\": \"foo\", \\n 7| \"id\": \"foo\", \\n",
"title": "Update Article — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1603_KNOWLEDGE_NODE-1",
"text": "https://api.devrev.ai/question-answers.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/beta/api-reference/question-answers/list-question-answers-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"question_answers\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"answer\": \"string\", |\\n| 6 | \"applies_to_parts\": [ |\\n| 7 | { |\\n| 8 | \"display_id\": \"string\", |\\n| 9 |",
"title": "List Question Answers (POST) | DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-42",
"text": "elements exist.\\nAPI Reference articles List Articles Post.\\n\\nPOST https:// api.devrev.ai / articles.list\\nLists a collection of articles.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for articles belonging to any of the provided parts.\\narticle_type list of \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nFilter for the type of articles. If this is not provided, then articles that are not content blocks are",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Sla Trackers Get Post — DevRev | Docs"
}
] |
e119826a-ea9c-4a47-89f7-689de2601f3d
|
operator to check for null value in custom ticket fields in workflow
|
[
{
"id": "ART-15487_KNOWLEDGE_NODE-50",
"text": "\"fields\": [ \"custom_fields.rca\" ], |\\n| > | \"require\": true |\\n| > | } |\\n| > | ] |\\n| > | } |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\nAny attempt to update a *bug* object to the *completed* stage without populating\\nthe *RCA* field is rejected.\\n\\nThe supported operators are `==`, `!=`, `&&`, `||`. The `expression` is a\\nbinary expression that must return a boolean value.\\n\\nThe `effects` array contains the list of effects of the condition. The following effects are supported:\\n\\n* `require`: Whether",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-54",
"text": "] \\n >| } \\n >| ] \\n >| }\\'\\n[/code] \\n \\nAny attempt to update a _bug_ object to the _completed_ stage without populating the _RCA_ field is rejected.\\n\\nThe supported operators are `==`, `!=`, `>`, `>=`, `<`, `<=`. The `expression` is a boolean expression that must return a boolean value.\\n\\nThe `effects` array contains the list of effects of the condition. The following effects are supported:\\n\\n * `require`: Whether the field must be set for the condition",
"title": "Object customization (Beta) — DevRev | Docs"
}
] |
5ad07830-4b93-44ab-8f7e-3e9a4d92d601
|
Vendor availability impact on day-to-day operations
|
[
{
"id": "ART-738_KNOWLEDGE_NODE-17",
"text": "level\\n Also, some vendors who didn\\xe2\\x80\\x99t grow up in the \\xe2\\x80\\x9cas a service\\xe2\\x80\\x9d era will need to change processes to embrace CI/CD (some may have)\\n A good ask here is how frequently changes are deployed\\n When something new comes out, we can react and enable rapidly; others may be slower to enable, leading to a gap between when something is \\xe2\\x80\\x9cavailable\\xe2\\x80\\x9d and \\xe2\\x80\\x9creally available\\xe2\\x80\\x9d\\n \\n \\n\\n\\nMost of the available",
"title": "DevRev | Built for AI (not by AI... yet)"
},
{
"id": "ART-4172_KNOWLEDGE_NODE-11",
"text": "available. Moderate decline in performance since workaround is available but hampers day-to-day operations.\\n\\n***Medium*** - An inconvenient problem exists, however a workaround is readily available and can be applied. This type of issue may cause inconvenience or delays in certain tasks or processes, but it does not prevent the business from functioning altogether. There is no financial loss and no impact on day to day operations.\\n\\n***Low*** - There is a misleading or unsatisfactory",
"title": "DevRev Service Level Agreement"
},
{
"id": "ART-970_KNOWLEDGE_NODE-95",
"text": "as you need to build things at a much more macro level\\n Also, some vendors who didn\\xe2\\x80\\x99t grow up in the \\xe2\\x80\\x9cas a service\\xe2\\x80\\x9d era will need to change processes to embrace CI/CD (some may have)\\n A good ask here is how frequently changes are deployed\\n When something new comes out, we can react and enable rapidly; others may be slower to enable, leading to a gap between when something is \\xe2\\x80\\x9cavailable\\xe2\\x80\\x9d and \\xe2\\x80\\x9creally",
"title": "The Story"
},
{
"id": "ART-991_KNOWLEDGE_NODE-2",
"text": "different outcomes, some positive and the poor experiences leading to me churning off a vendor.\\n\\nExample 1: Bad\\n\\nIn my role, I produce many videos for external enablement, and we leverage a mix of YouTube and another vendor, which I will refer to as \\xe2\\x80\\x9cFoo.\\xe2\\x80\\x9d\\n\\nOne evening, I had trouble uploading videos I worked late to produce, so I contacted their support to see what was happening. I heard back the next day, and this was the response:\\n\\n\\xe2\\x80\\x9cHi there,\\n\\nThank",
"title": "Why Poor Support May Be Costing You More Than You Think"
},
{
"id": "ART-2133_KNOWLEDGE_NODE-46",
"text": "people (engineers, designers, and developers). For example, a meaningful awareness of an external service provider\\xe2\\x80\\x99s (a) noti\\xef\\xac\\x81cations and outages, (b) advisories and vulnerabilities, (c) new capabilities, and (d) economics of usage, all via automations, is crucial for reducing security risks and \\xef\\xac\\x81nancial surprises down the line. Similarly, a continuous understanding of an engineer\\xe2\\x80\\x99s (a) skills and contributions, (b) deep work metrics, and (c)",
"title": "The Essential Methodology: Less but Better"
},
{
"id": "ART-991_KNOWLEDGE_NODE-11",
"text": "ready, they proactively contacted us to get us on the program and worked with us to ensure everything was operating as expected. During the cutover, they were on a call live with us to ensure everything worked as expected. We ran into a few hiccups, but they helped troubleshoot and solve with us live.\\n\\nThis is an excellent example of a partnership, not a traditional vendor/client relationship. They were honest about the lack of a feature (this builds credibility), but they were also proactive",
"title": "Why Poor Support May Be Costing You More Than You Think"
},
{
"id": "ART-16189_KNOWLEDGE_NODE-9",
"text": "Increased collaboration between support, engineering, and customer success\\n* Proactive engagement through real-time issue visibility and alerts\\n* Centralized communication and streamlined workflows\\n* Scalable operations without requiring a dedicated people manager\\n\\nWith DevRev, FOSSA shifted from reactive support to a connected, efficient, and proactive experience.\\n\\nWe evaluated our legacy vendor\\xe2\\x80\\x99s AI capabilities, and it was difficult to even get them to come to the table. In",
"title": "FOSSA’s Unified Support Strategy for Elevated Customer Experience"
},
{
"id": "ART-2957_KNOWLEDGE_NODE-0",
"text": "b'Summary\\n\\nDescription: On November 7, 2024, we identified significant latency issues affecting our Web Monitoring API and other domains routed through Fastly. The issue was resolved later the same day by rerouting traffic for the impacted service.\\n\\nSeverity: High\\n\\nImpact: The latency affected the performance of the Web Monitoring API and other DevRev services, potentially causing delays in customer workflows and impacting user experience. Root Cause Analysis\\n\\nThe latency was traced",
"title": "Increased Latency on Web Monitoring API - November 7, 2024"
},
{
"id": "ART-4172_KNOWLEDGE_NODE-15",
"text": "(<https://support.devrev.ai/>).\\n\\n### 6.The following services shall be out of scope\\n\\n* Services related to Third-Party Products\\n* Errors in any end-user data or other information supplied by the Customer\\n* Errors not attributable to the DevRev service\\n\\n### 7. Holiday schedule\\n\\n**INDIA(APAC) Holiday Schedule**\\n\\n| Dates | Dates cont. |\\n| --- | --- |\\n| January 1 | May 1 |\\n| January 14 | August 15 |\\n| January 26 | August 27 |\\n| March 14 | October 1 |\\n| March 30 | October 20 |\\n|",
"title": "DevRev Service Level Agreement"
},
{
"id": "ART-4172_KNOWLEDGE_NODE-13",
"text": "24 Business Hours |\\n\\n*Business Days: Monday - Friday (Saturday and Sunday coverage provided for incidents only)* \\n*Response commitments remain void for the region during the holidays mentioned below, except for incidents*\\n\\n*\\\\*No SLA promised on tickets other than BUGS*\\n\\n### 3. Support Channels\\n\\n* Chat ([www.DevRev.ai](http://www.devrev.ai/) | [https://app.DevRev.ai](https://app.devrev.ai/))\\n* Email ([[email protected]](mailto:[email protected]))\\n* Support Portal",
"title": "DevRev Service Level Agreement"
}
] |
3c39d4b7-5a9b-470e-aa49-a3c138e97349
|
workflow filter based on customer account variable
|
[
{
"id": "ART-12392_KNOWLEDGE_NODE-25",
"text": "| --- | --- |\\n| Account created | Filter conditions | Account object |\\n| Account updated | Filter conditions | Account object |\\n| Contact created | Filter conditions | Customer User object |\\n| Contact updated | Filter conditions | User object |\\n| Enhancement updated | Filter conditions | Enhancement object |\\n| Incident updated | Filter conditions | Incident object |\\n| Issue created | Filter conditions | Issue object |\\n| Issue linked With object | Filter conditions | Issue and linked",
"title": "Triggers | Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1976_KNOWLEDGE_NODE-28",
"text": "scenarios\\n----------------------------\\n\\n* Ticket routing based on customer inquiry keywords.\\n* Group-specific routing based on customer account assignments.\\n* Assignment routing based on severity and subtype.\\n* Custom field and tag-based routing.\\n* First responder ticket assignment.\\n\\nSystem requirements\\n-------------------\\n\\n* Administrator privileges are required for workflow deployment and execution.\\n* User status (active/away) is configurable through the profile",
"title": "Routing | Computer for Support Teams | DevRev"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-464",
"text": "set, then \"after\" is used.\\nAllowed values: after before\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string Optional\\nFilters for work reported by any of",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-451",
"text": "provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-37",
"text": "\\n{{Ticket\\xc2\\xa0Created\\xc2\\xa0>\\xc2\\xa0Output\\xc2\\xa0>\\xc2\\xa0Reported\\xc2\\xa0By\\xc2\\xa0>\\xc2\\xa0Rev\\xc2\\xa0Org\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0Name}}.\\xe2\\x80\\x9d\\n\\n\\n\\nDelay\\n\\n\\n\\nDuration: 2 minutes\\n\\n\\n\\nIf-else\\n\\n\\n\\nAttribute:\\xc2\\xa0Ticket\\xc2\\xa0Created/Output\\xc2\\xa0>\\xc2\\xa0Applies\\xc2\\xa0to\\xc2\\xa0part\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0ID \\nOperator: Equals \\nOperand: CAPL-18\\n\\n\\n\\nTicket \\ncreated\\n\\n\\n\\nEnd\\n```\\n\\n[### Workflow action",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-34",
"text": "button toolbar.\\n4. Set your triggers. You can have multiple triggers within a single workflow.\\n5. To configure your workflow, utilize the data reference pane to select values from previous nodes.\\n6. Connect steps with multiple paths as needed, allowing for the management of complex workflows on one canvas.\\n7. To add conditional logic, use a control step.\\n\\n Select a value for the LHS; select the appropriate operator; and enter or select a value for the RHS, which can be a literal value",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-7",
"text": "specified user(s).\\n\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\n\\nFilters for custom fields.\\n\\ndisplay_name list of strings Optional\\n\\nArray of display names of accounts to be filtered.\\n\\ndomains list of strings Optional\\n\\nDomains for accounts to be filtered.\\n\\nexternal_refs list of strings Optional\\n\\nArray of references of accounts to be filtered.\\n\\nfirst integer Optional\\n\\nThe number of accounts to return. The default is",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1560_KNOWLEDGE_NODE-517",
"text": "used.\\n\\nAllowed values: after before\\nopportunity.account string Optional\\n\\nFilters for opportunities belonging to any of the provided accounts.\\n\\nopportunity.contacts string Optional\\n\\nFilters for opportunities with any of the provided contacts.\\n\\nopportunity.subtype string Optional\\n\\nFilters for opportunity with any of the provided subtypes.\\n\\nowned_by string Optional\\n\\nFilters for work owned by any of these users.\\n\\nreported_by string Optional\\n\\nFilters for work reported by any of",
"title": "Assign (Beta) — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-440",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-441",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-517",
"text": "used.\\n\\nAllowed values: after before\\nopportunity.account string Optional\\n\\nFilters for opportunities belonging to any of the provided accounts.\\n\\nopportunity.contacts string Optional\\n\\nFilters for opportunities with any of the provided contacts.\\n\\nopportunity.subtype string Optional\\n\\nFilters for opportunity with any of the provided subtypes.\\n\\nowned_by string Optional\\n\\nFilters for work owned by any of these users.\\n\\nreported_by string Optional\\n\\nFilters for work reported by any of",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-446",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-440",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-442",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-444",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-440",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-443",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-443",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-446",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-443",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-446",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-446",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-446",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-442",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-448",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-448",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Self Post — DevRev | Docs"
}
] |
324e4314-929d-4d55-829b-00d2b0cfb363
|
create CRM to track leads and potential clients
|
[
{
"id": "ART-2933_KNOWLEDGE_NODE-1",
"text": "`accounts-create` and `rev-users.create` API. You can also [create accounts manually in DevRev app](https://docs.devrev.ai/product/customers#add-new-customers).\\nThe `accounts-create` API is used to create [accounts](https://docs.devrev.ai/product/grow#-account) which represents a customer organization and it holds information about the company, including its name, address, industry, domain, and website address.\\n\\nThe `rev-users.create` API is used to create",
"title": "Account creation | DevRev | Docs"
},
{
"id": "ART-6175_KNOWLEDGE_NODE-24",
"text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Airtable](/docs/automations/airtable)\\n\\nAirtable\\n========\\n\\nThe **Airtable** snap-in automates lead intake from Airtable form submissions by mapping responses to DevRev contacts, accounts, and custom objects. It supports field mapping, duplicate detection, tagging, and ownership assignment using custom configurations. Submissions are processed in real time, enabling seamless CRM integration and streamlined data",
"title": "Airtable | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2002_KNOWLEDGE_NODE-31",
"text": "**Group** conditions across various vistas in DevRev to track specific work, capacity, and more.\\n\\nYou can add custom attributes to opportunities to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\n### External reference\\n\\nWhile ingesting customer identity into DevRev, customer information coming across channels must be matched to the same record. \\nFor example, a customer record created by you using APIs should",
"title": "Contacts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-15502_KNOWLEDGE_NODE-5",
"text": "marketing campaigns on DevRev. This guide goes through the process of creating a \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d custom object with relevant fields.\\n\\nAll DevRev objects require a schema. First, create a schema for the \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d custom object. Make sure to replace the `<TOKEN>` with your API token.\\n\\n### Create custom objects\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/schemas.custom.set\\' \\\\ |\\n| > | --header \\'Content-Type:",
"title": "Custom objects | DevRev | Docs"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-31",
"text": "conditions While creating custom schema\\n\\nThis can be handled by our team. Kindly reach out to us, and we\\xe2\\x80\\x99ll be happy to assist you with setting up a custom schema. Would you like us to create a ticket for this?\\n\\nAPI for stage customizationThis can be handled by our team. Kindly reach out to us, and we\\xe2\\x80\\x99ll be happy to assist you with setting this up. Would you like us to create a ticket for this?\\n\\nStage customization (e.g., customizing workflow stages for tickets,",
"title": "Support queries related playbook"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-356",
"text": "Create.\\n\\nPOST https:// api.devrev.ai / rev-users.create\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of the account to which the created Rev user is associated.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev user.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-353",
"text": "rev-users.create\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of the account to which the created Rev user is associated.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev user.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nThe schema",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-4096_KNOWLEDGE_NODE-1",
"text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Rev Users](/public/api-reference/rev-users/create)\\n\\n# Create Rev User\\n\\nPOST\\n\\nhttps://api.devrev.ai/rev-users.create\\n\\nTry it\\n\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\n\\n### Request\\n\\nThis endpoint expects an",
"title": "Create Rev User — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-359",
"text": "rev-users.create\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of the account to which the created Rev user is associated.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev user.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nThe schema",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-359",
"text": "rev-users.create\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of the account to which the created Rev user is associated.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev user.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nThe schema",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-357",
"text": "rev-users.create\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of the account to which the created Rev user is associated.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev user.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nThe schema",
"title": "Update — DevRev | Docs"
}
] |
f95a98db-4fc1-46d8-8128-65213477b402
|
Next SLA Target field logic
|
[
{
"id": "ART-1986_KNOWLEDGE_NODE-42",
"text": "Target\\n------------------------------------\\n\\nIn order to filter tickets based on SLA, you can use the **Next SLA Target** filter.\\nHere\\xe2\\x80\\x99s how the filter works:\\n\\n* **All**: Filters all tickets that currently have an SLA applied to them. It will not filter tickets that had an SLA applied in the past and have been completed.\\n* **Breached since**:\\n\\n + **Any**: Filters all tickets that breached SLA, irrespective of when they were breached.\\n + **Over an hour**: Filters all",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-40",
"text": "conversation moves to any stage except Waiting on User |\\n\\nViewing SLAs\\n------------\\n\\nThe SLA targets applied to a particular conversation can be viewed in the **Inbox** and the **Conversation Detailed** view. For a ticket in any of the ticket vistas.\\n\\nWhen there are two active metrics, vista displays the one closest to the breach. In the case of a conversation where both the first response and full resolution metrics are active, and the first response is due in five minutes but the full",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
}
] |
End of preview. Expand
in Data Studio
DevRev Search Dataset
Summary
The DevRev Search Dataset contains transformed and anonymized user queries on DevRev's public articles, paired with relevant article chunks that answer them. It is designed to benchmark enterprise search and reranking systems. The dataset also includes test queries along with the underlying article chunks used for retrieval.
Dataset Details
- Curated by: Research@DevRev
- Language: English
- Intended Use: Evaluation of search, retrieval, and reranking models in enterprise support contexts
Dataset Structure
annotated_queries.parquet— Queries paired with annotated (golden) article chunksknowledge_base.parquet— Article chunks created from DevRev's customer-facing support documentationtest_queries.parquet— Held-out queries used for evaluation
Quick Start
from datasets import load_dataset
annotated_queries = load_dataset("devrev/search", "annotated_queries", split="train")
knowledge_base = load_dataset("devrev/search", "knowledge_base", split="corpus")
test_queries = load_dataset("devrev/search", "test_queries", split="test")
Dataset Creation
Curation Rationale
There is a lack of publicly available datasets representing enterprise support search. This dataset addresses that gap, enabling fair and consistent evaluation of enterprise-focused search and reranking systems.
Source Data
- Queries: Transformed and anonymized versions of real user queries on DevRev's public articles.
- Knowledge Base Articles: Segmented (chunked) excerpts from DevRev’s customer-facing support documentation.
Annotations
- Annotation Process: An automated proprietary pipeline identifies the most relevant article chunks for each query.
- Annotators: Fully automated system; no human annotators were used.
- Validation: Internal validation was conducted by selecting a representative sample of the automatically generated annotations, which were then manually reviewed by human evaluators to verify their correctness and ensure they meet the desired quality standards.
Personal and Sensitive Information
All user queries were anonymized and stripped of any identifying or sensitive data. No personal information is included.
Uses
- Primary Use: Training and evaluation of enterprise search, retrieval, and reranking models.
- Example Tasks:
- Query-to-document retrieval
- Reranking
Product Impact
This dataset played a key role in honing Computer by DevRev. Learn more about Computer here: Computer by DevRev | Your New Conversational AI Teammate
Citation
If you use this dataset, please cite:
BibTeX:
@dataset{devrev_search_2025,
title={DevRev Search Dataset},
author={Research@DevRev},
year={2025},
url={https://huggingface.co/datasets/devrev/search},
license={CC-BY-4.0}
}
- Downloads last month
- 26