2 Replies Latest reply on Dec 12, 2017 9:01 AM by AlasdairRobertson

    Knowledge Article - Versioning?

    MarkLarvo Specialist

      Has anyone come up with a way to use the KnowledgeNumber and KnowledgeVersion fields to keep revisions of articles?


      At first I considered using an extra field to store the v1 KnowledgeNumber but that would require editing all sorts of layout forms and who knows what else.


      Now, since I see KnowledgeNumber is not a unique field I was considering using this field but making sure our Quick Action marked the prior version Archived. I am wondering how searches and automated urls might work. If they honor the viewing restrictions I think we will be okay.


      Does anyone have insight into how these fields were meant to work? I'll post my findings.



        • 1. Re: Knowledge Article - Versioning?
          michael.odriscoll SupportEmployee

          Hi Mark,


          Thanks for posting to the Ivanti Community!


          Sorry that it seems no one has the answer to be able to assist you on this yet.  Did you manage to get any further information on this? Please share anything you deem useful and the community may be able to offer some help.


          If not then please do consider the other ways to engage with us to get assistance:


          • 2. Re: Knowledge Article - Versioning?
            AlasdairRobertson ITSMMVPGroup

            Add depends on how far you wish to take knowledge and revisions.  It is possible to create some rather complex knowledge re-versioning using quick actions and workflows to clone the existing article increase the version number and then push through and approval process.  Once the approval is gained the old article can be archived automatically.  You will need a new relationship to be created between the old and new versions ideally, thinking about it you could have a version tab which lists the old versions and links directly to them.


            OOTB the knowledge number is generated from a counter, the field in my database is set to unique at the FRS_Knowledge object level.  It comes from a counter using the $(GetNextCounter()) function.

            The version field is just a manual field to use but as I mentioned above could be automated.