Recent Content
How do I get the article ID in Freemarker in a TkbArticle?
This is Community Classic. I'm trying to write a component to display something from a hidden field (canonical_url) while on the page of a TkbArticle. It doesn't appear that either page.context.message.id or env.context.message.id work in anything Tkb related. What other options do I have to retrieve this information in the context of the page itself?
400/404 error on POST request
Hey, I'm trying to do my very first POST API call and currently getting stuck. I know there are other solutions for what I'm trying to do, but I'm also trying to learn something rather than straight up copying & pasting. <#assign boardID = coreNode.id /> <button id="subscribe">Subscribe</button> <@liaAddScript> (function($){ $(document).ready(function(){ $("#subscribe").on( "click", function() { $.ajax({ url: "/api/2.0/subscriptions", dataType: 'json', data: { "data":{ "type":"subscription", "target":{ "type":"board", "id":"blueprints" } } }, method: 'POST' }).done(function(response) { console.log('Success'); }).fail(function() { console.log('Fail'); }) }); }); })(LITHIUM.jQuery); </@liaAddScript> When I click my button on the page, I get a 404 error in the console: GET https://community-stage.blueprism.com/api/2.0/subscriptions?data%5Btype%5D=subscription&data%5Btarget%5D%5Btype%5D=board&data%5Btarget%5D%5Bid%5D=blueprints 404 (Not Found) I assume I'm doing something wrong, but I can't figure out what. I've tried subbing the variable for the ID of the board too and the URL is the same, with the same 404 error. The only thing that's sprung to mind is that the API's don't work with the CNAME and I need to use the original domain for our staging site? Thanks in advance.Online User Count is Completely Wrong
I'm trying to get an accurate count of online users and it's quite obvious the count is completely wrong just by looking at the results I'm encountering on my staging environment. The LIQL query used is fairly simple: SELECT count(*) FROM users WHERE online_status='online' Given the number of people who access our staging server, I would expect the result of this to be a low single digit number. Instead, I got a result of over 30 users. So I dug into the API results: SELECT login,last_visit_time FROM users WHERE online_status='online' The results list users with last visit times from 2020 and 2021 as well as users from earlier in 2022 that I know for a fact aren't online. How is Khoros defining an "online user" here? Is the behavior I'm seeing a bug or expected behavior?Escalating Support Cases
Some tips before escalating In the case portal, you have the ability to set/change the "Customer Priority" field between low, normal and high. When issues are urgent but not necessarily world ending, changing the priority to "high" will push it up the list of issues based on your support level, which is a good way to get support's attention to an issue. One thing to avoid if possible is creating a case and escalating it that same day without a strong reason. Same day escalations are generally pushed back on to allow them to go through the standard support triage process and gather all necessary information before bringing in other experts or teams, but short-cutting tends to be disruptive to that process and introduces further delays. While it is important to stay in close contact with your CSM or account rep, we strongly recommend bypassing them for escalations and instead escalating directly via the case portal. Ad-hoc escalations create back channels and can duplicate efforts, which has resulted in delays or confusion around escalations. CSM's are also informed around escalations automatically, so they will be aware. When should I escalate? You should escalate when there is urgency involved in a support ticket. This would include issues such as, but not limited to: Time constraints (SSL cert expiring, deadlines, events, etc.) A major impaired function that does not qualify as an severity 1 issue SLA missed for first response Unresponsive or lack of updates in a case While we'll do our best to keep it to a minimum, there will be times when escalated issues will not be accepted as an escalation. If/when that happens, an automated reply will be sent to inform the user who originally escalated the case. Decisions around escalations are entirely at the discretion of the team responsible for escalations. Additionally, the escalation feature is not designed to replace the outage alias. Any issue which qualifies as being of outage severity should continue to go through the standard outage process of emailing outage@lithium.com or setting the case severity to "1". When can I escalate? All Severity 1 cases (outages) are automatically escalated to our Mission Critical Support team and thus do not require further escalation. Cases that were submitted with a lower severity rating can be escalated four (4) hours after the original submission. Can I escalate outages? All severity 1 issues are considered outage level and it's not necessary to escalate since an on-call team is available 24/7/365 for issues that qualify. S1 cases are already at the highest and most visible level possible. How do I escalate a support case? Aftera case has been created, the option to escalate it will be available. Simply open the desired support ticket within the Case Portaland click Escalate Caselocated in the escalation information section. Anew form displays along with some details and instructions. On that form, provide a summary of why the case needs to be escalated to an Escalation Manager for review within 4 business hours. After you've filled out the escalation summary and submitted the request, an alert is sent to an Escalation Manager for review. An Escalation Manager will review the request and reply directly in the case you escalated with a decision or plan of action. What if I'm not satisfied with the current escalation decision or progress? Should you be unsatisfied with the results of your case escalation, you have the option to go up a higher level by clicking the "Escalate Case" button again. When the "Escalate Case" button is used again, you'll be presented with a different form acknowledging the next-level escalation and again requesting you provide an explanation around the reason for escalating again / higher. Once submitted, an Escalation Manager will review the request and respond directly within the escalated case. You can perform this process multiple times. The higher the escalation, the more members of Leadership or Management will be involved. Here's a breakdown of the various levels and what occurs: Level 1: The case is escalated to our senior support engineers, team leads and managers. Level 2: All of the previous team is alerted, but the escalation is extended to senior managers, directors and your account's Customer Success Manager (CSM). Level 3: All of the previous manager groups from Level 2 are alerted, but in addition, the Senior Director of Global Technical Support will be included. A full analysis will be completed to understand why this case needed an escalation to this level. Level 4: All of the managers from Level 3 are alerted, but our VP of Support is also alerted and will take personal responsibility to drive through to completion.
TinyMceEditor is undefined
Hi, I have a simple custom component: <form id="pmUpdateForm"> <textarea rows="" cols="" id="pmUpdate"></textarea> </form> <@liaAddScript> ;(function($) { $(document).ready(function() { tinymce.init({ selector: 'textarea#pmUpdate', height: 150, menubar: false, plugins : "paste", paste_text_sticky : true, setup : function(ed) { ed.pasteAsPlainText = true; } }); }); })(LITHIUM.jQuery, LITHIUM.TinyMceEditor); </@liaAddScript> I added the above component into one of the quilts. After the SDK push I always see Uncaught ReferenceError: tinymce is not definederror. I know why this error occurs but w.r.t Khoros, I am not able to figure out where to look. There is no official documentation about tinyMceEditor in atlas on how to use it.Community Text - First Name Text Key
In Studio > Text Editor > Community TextI want to update the text-key general.welcome = Welcome back, {0}! To something like: general.welcome = Welcome back, ${profile.name_first}! But I don't know the text-key for the First Name in a user's Personal Information setting. Currently we are using general.welcome = Welcome back, {0}! And {0} is their username. We would like to personalize the message with their first name instead of their username. Does anyone know what text-key I can use to pull a users first name from their personal information / settings / profile? Thank you! DaveUrgent: Case Sensitivity w/ SSO
Our people system changed (salesforce, workday, whatever), and several users are saying "It's asking me to create a username!" Turns out: the OLD people system passes parikshita.sahoo@duckcreek.com The NEW people system passes Parikshita.Sahoo@duckcreek.com Apparently Khoros sees these as DIFFERENT users (due to capitalization changes). I submitted a support ticket, but the response indicated it's going to take a bunch of back & forth to help them recreate this thing. Which leads me to straight up ask you all -Has anyone else ran into case sensitivity issues before? In collaboration with our IAM team, I have a "plan" but it's not an easy one (transform to lowercase on the B2C front, and simultaneously batch some Khoros API calls to change all users' SSO IDs to lowercase. But it seems outright silly that Khoros cares about case sensitivity. Has anyone solved this before? Is there a checkbox I'm missing?
