How does custom component built for Next Experience impacts application certification credits?

ArjunBasnet
Tera Guru

Hello there,

some concern regarding custom component development.
We know that Next Experience's custom component reside on their own scope, and a technology "build partners" have a certain certification credits (number of application scopes available).

When custom_component_x is included in experience of product_1, then would it be enough to certify product_1? Or custom_component_x has to go through it's own certification process?


I hope custom component when incorporated into the product would not consume certification credit.

Thanks.

 

1 ACCEPTED SOLUTION

ArjunBasnet
Tera Guru

For Future Readers

Upon discussing with Certification Team it was clarified that "Custom Component" if chosen to be part of the application scope, there won't be issue with certification credits. However, if Custom Components are included in separate new scope and the existing product (application) depends on it. The separate new scope has to go through it's own certification. All in all Custom Component could share same scope, these are differentiated with used scope identifier.

View solution in original post

3 REPLIES 3

Brad Tilton
ServiceNow Employee
ServiceNow Employee

Hi Arjun,

This is really a question for the certification team. I do know there are a number of partner store apps that have custom components incorporated into them on the store already, so they should be able to answer that for you.

Thanks Brad for the info that suggest me that my assumption might be correct, however will clarify from certifiers.

ArjunBasnet
Tera Guru

For Future Readers

Upon discussing with Certification Team it was clarified that "Custom Component" if chosen to be part of the application scope, there won't be issue with certification credits. However, if Custom Components are included in separate new scope and the existing product (application) depends on it. The separate new scope has to go through it's own certification. All in all Custom Component could share same scope, these are differentiated with used scope identifier.