Outdated state and Valid To field knowledge

[alexm1]

Hello,

I'm trying to set the valid_to date on the knowledge form based on the workflow status of the article. For example if workflow status is review date is set to current day. 

I'm doing this from a business rule and all conditions work great except for when workflow state is Outdated. Nothing happens  when workflow state changes to Outdated. We are using versioning. 

How conditions work:

If state is Draft  - valid_to is populated with a fixed date

if state is review - valid_to is populated with  current date

if state is published - valid_to is populated with current date + 1 year

If state is pending retirement - valid_to is populated with current date

if state is retired - valid_to is populated with current date

if state is outdated - valid_to should be populated with the current date but it's not, date stays unchanged. 

Need some help to change this date to current date when workflow status changes to Outdated.

Thanks,

Alex

[alexm1]

Same thing with dvp script.

Noticed that if you go to a kb after it was set to outdated and do any modifications and hit save, then the valid_to date is updated. 

But if it goes from published to outdated via the versioning system the field does not get updated. 

[alexm1]

And yes I have the condition when workflow state changes

Thanks,

Alex

[Brad Tilton]

Is outdated a choice you've added? How does it go from published to outdated?

What if you run the BR at 1000000 to make sure it runs after anything else that may be setting field values?

[alexm1]

Outdated is OOTB. I think it comes with the Knowledge Management Advanced plugin.

Outdate works like this:

1. Create an article > State is Draft - article version is 0.x
2. Click Publish > State changes to Review and approval is sent  - article version is 0.y

3. Article is Approved, state changes to Published. - article version is 1.x

4. Click on Checkout button, state changes to Draft and a message is displayed saying "A new version of the article is created for revision." - article version changes to 2.x

5. Click Publish > State changes to Review and approval is sent  - article version is 2.y

6.  Article is Approved, state changes to Published. - article version is 2., at this point old version 1.x becomes Outdated. 

This is all OOTB. 

Hope that what I described makes sense. 

[annc_]

I came across the same issue. Has anybody found a solution to this?