For my customization, I need to understand few points in metadata editor like
how the view mode (by group, by package etc.) is handled in code.
I can see metadata.update.new or …create.new services are called with a lot of parameters. I guess the parameter currTab specifies the currently selected view mode, but what code (if possible, point in the code) in the background handles this?
how online resources are generated (shown in RHS panel in editor page)
I can see xml.relation service being associated with it, but what java code?
how suggestions are generated (shown in RHS panel in editor page)
Again, what code is tied to metadata.suggestion service?
If you can give me enough info on this, that would be great but even partial info to get me started on this is appreciated.
how the view mode (by group, by package etc.) is handled in code.
I can see metadata.update.new or …create.new services are called with a lot of parameters. I guess the parameter currTab specifies the currently selected view mode, but what code (if possible, point in the code) in the background handles this?
how online resources are generated (shown in RHS panel in editor page)
I can see xml.relation service being associated with it, but what java code?
how suggestions are generated (shown in RHS panel in editor page)
Again, what code is tied to metadata.suggestion service?
If you can give me enough info on this, that would be great but even partial info to get me started on this is appreciated.
Thanks
Ameet
How ServiceNow helps IT people transform IT departments:
Consolidate legacy IT systems to a single system of record for IT
Standardize and globalize service processes across IT
Thanks Francois for the Jeeves link, but is that document relevant? that was created in 2005, so I fear much of it will not apply to the latest code… can that be true?
how the view mode (by group, by package etc.) is handled in code.
I can see metadata.update.new or …create.new services are called with a lot of parameters. I guess the parameter currTab specifies the currently selected view mode, but what code (if possible, point in the code) in the background handles this?
how online resources are generated (shown in RHS panel in editor page)
I can see xml.relation service being associated with it, but what java code?
how suggestions are generated (shown in RHS panel in editor page)
Again, what code is tied to metadata.suggestion service?
If you can give me enough info on this, that would be great but even partial info to get me started on this is appreciated.
Thanks
Ameet
How ServiceNow helps IT people transform IT departments:
Consolidate legacy IT systems to a single system of record for IT
Standardize and globalize service processes across IT
On Wed, Sep 11, 2013 at 4:12 PM, Ameet Chaudhari
<ameet.chaudhari@anonymised.com>wrote:
Thanks Francois for the Jeeves link, but is that document relevant? that
was created in 2005, so I fear much of it will not apply to the latest
code.. can that be true?
Hi,
Development of Jeeves has been quite frozen on the last years, as nobody
needed further implementations. The documentation is still valid.
Regarding your first question, probably you are looking on the XSL
transformations that happen just before jeeves returns the view. Hope this
hint helps you.
María.
Ameet
On Tue, Sep 10, 2013 at 6:14 PM, Francois Prunayre <fx.prunayre@anonymised.com>wrote:
For my customization, I need to understand few points in metadata editor
like
You should probably look into Jeeves manual so you can get a better idea
of the link between the service name (eg. xml.relation defined in
config-*.xml) and the Java class and XSL used by the service.
1. how the view mode (by group, by package etc.) is handled in code.
I can see metadata.update.new or ...create.new services are called with
a lot of parameters. I guess the parameter currTab specifies the
currently selected view mode, but what code (if possible, point in the
code) in the background handles this?
2. how online resources are generated (shown in RHS panel in editor page)
I can see xml.relation service being associated with it, but what java
code?
3. how suggestions are generated (shown in RHS panel in editor page)
Again, what code is tied to metadata.suggestion service?
If you can give me enough info on this, that would be great but even
partial info to get me started on this is appreciated.
Thanks
Ameet
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
Thanks Francois for the Jeeves link, but is that document relevant? that was created in 2005, so I fear much of it will not apply to the latest code… can that be true?
Hi,
Development of Jeeves has been quite frozen on the last years, as nobody needed further implementations. The documentation is still valid.
Regarding your first question, probably you are looking on the XSL transformations that happen just before jeeves returns the view. Hope this hint helps you.
María.
Ameet
How ServiceNow helps IT people transform IT departments:
Consolidate legacy IT systems to a single system of record for IT
Standardize and globalize service processes across IT
how the view mode (by group, by package etc.) is handled in code.
I can see metadata.update.new or …create.new services are called with a lot of parameters. I guess the parameter currTab specifies the currently selected view mode, but what code (if possible, point in the code) in the background handles this?
how online resources are generated (shown in RHS panel in editor page)
I can see xml.relation service being associated with it, but what java code?
how suggestions are generated (shown in RHS panel in editor page)
Again, what code is tied to metadata.suggestion service?
If you can give me enough info on this, that would be great but even partial info to get me started on this is appreciated.
Thanks
Ameet
How ServiceNow helps IT people transform IT departments:
Consolidate legacy IT systems to a single system of record for IT
Standardize and globalize service processes across IT
