I need one suggestion, I am planning to create a new module requirement. so what are the technical aspects i need to look at ?
I think i need to look at dbdict(new table), FD,FC, Links,display option, Menu, User Profiles, capabilitiy words,notification and reports.
I am missing something ??
Start wtih a new Document Engine Object. By using an Object, you get the capablities to configure queues and views, call notifications, etc. with a lot less work. It saves a lot of time.
You can copy the DEFAULT object to start and modify as needed.
In a 9.4x Codeless system, there is a guide for adding confifureing a new PD module available.
First thing you need to create is a object,Inside the object you can create you own states.processes,Display screens and Display options.I will recommend to use some out of the box states i.e db.view and db.search which will help you initially and later on create your own states,processes.You missed Object record.
Thanks @John Stagaman
I have a one more query if you dont mind.
This is regarding licensing strategy for new module. I understand in sm licenses works based on the modules, so what will be the case when we build new custom modules ??
Thanks in advance..
Users of the custom module fall under the login licenses/foundation.
Note that building a custom module to avoid licensing a product module that provides the same functionality can be an issue (e.g. modifying incident to allow catalog-based requests and fulfillment flows to be implemented without using SRC or Request). But so long as that's not the case, I don't think there are any issues. I've built a custom on-call module, for example, that was integrated into the OOB modules.