Custom component in Ribbon

Tommy Jensen
Giga Guru

Have anybody been able to use a custom component as a Ribbon component?

I deployed my simple component. It only displays a text.

Then I added ACL's on the table: sys_aw_ribbon_component

and created a record there that points to my component.

Then in "Ribbon settings" I configured it to display on my record in workspace.

When a record with this Ribbon is displayed. I can see that space has been assigned to the component and inspecting the page I can actually see the component directive but the content is not rendered. And there is no errors at all in the console.log.

So what could I be missing?

find_real_file.png

running locally this is what it displays:
find_real_file.png

 

This is the component, super simple:

import { createCustomElement, actionTypes } from '@servicenow/ui-core';
import snabbdom, { Fragment } from '@servicenow/ui-renderer-snabbdom';
import styles from './styles.scss';

import '@servicenow/now-heading';

const view = (state, { dispatch, updateState }) => {
	return (
		<Fragment>
			<main className="now-checklist">
				<div>
					<now-heading label="Test ribbon" />
				</div>
			</main>
		</Fragment>
	);
};

createCustomElement('x-80603-my-ribbon', {
	renderer: { type: snabbdom },
	view,
	styles: styles
});
25 REPLIES 25

Satyanarayana C
ServiceNow Employee
ServiceNow Employee

Hi,

Could you please try one of the below. 

1. Try clearing cache - /cache.do

2. Try clearing browser cache or open the workspace in an incognito window.

3. In the ribbon component table, click on the 'UX Component' reference which will navigate to - sys_ux_lib_component table. In this, update the source script field by searching your custom component.

Thanks

I have done all that. If that is all you can provide then I kindly ask you to not reply on my questions as your questions are not helpfull in any way.

Hi,

Thanks for taking time and trying out the suggestions. If you find a solution, could you please post it here.

Thanks

DrewW
Mega Sage
Mega Sage

What version are you on?  I was told by ServiceNow to get this to work properly that you need to be on Orlando Patch 3.