Rejecting Submissed content with the use of a custom field - Field not appearing when filtering

Hi,
We are doing some tests with FlexiContent to be able able to Reject a content submitted to workflow system. (New article, version revisions,...).
Joomla Version : 3.4.4
FlexiContent Version : 3.0.8

We want our authors/editors (and even publishers) to be able to see which articles have been rejected.
It is suggested here to use a custom field to handle this need :
www.flexicontent.org/forum/20-general-su...ent-submissions.html

So we created a new field, made it only editable by publishers and admins, and we made it "filterable".
Field :





But there is a problem when we want to filter using this field.
As when we Reject an article, we do not save it as current (because we don't want it to be published) :





=> The article does not appear on the item list when we use the filter :



Here we even do not have the Rejected selection, because as the rejected version will never be the "current" one's, no articles will have this value in the search.

So the custom field solution is not really working for us because we want the writers to be able to see / filter the articles which have been rejected.

How would you do to Reject Articles with FC ?
Is it possible to indicate in a custom field that when we use a filter on it, it has to look in the last version and not the current ?

It may be a good idea to add the support for Rejection with new statuses in FC Workflow system ?
May be :
Rejected :: Pending => For articles not published
Rejected :: Published => For rejected versions of already published articles.

Thanks in advance.

Hello

you can not save individual fields

- but in your case you want to set this field in which version? set it in the current ?

so that if your lists his/her items, then will see a
field sub-status ("last submitted changes approved") --> not approved


You could make this field have "access level" e.g. "Site authors",
so that it is visible by the authors by not by the site visitors

then
1. load current version
2. set the field and then save


-- but i understand that the above will have the problem that the frontend users cannot load the older versions
thus if you do above, then they will not be able to load the version that was not approved and make corrections
instead they will have to re-write the changes


-- in the end, i think that best way is to have a field property:
"Field is not subject to versioning"

thus if someone e.g. administrator can edit the field then he can save a value that will be
- loaded in item form
- and viewed
regardless of versioning

Hi

Thanks for the answer.
I understand what you suggested for the first solution, but like you said, frontend user will then not be able to see the version not approved and will have to rewrite everything.
So we actually can't do that for the workflow we want to have for our authors.

For the "Field is not subject to versioning" solution, I agree with you. It could be a great addition to the field's management, and can resolve our issue.
Is it planned in future version ?

Another question linked to the first :
Is it possible to create Statuses/ states ?
It could help us for our need of articles rejection.

Is there anything planned for the rejection of items in the worklow of FC ?
The second solution you proposed, about a field which is not affected by versions, is planned ? or already exists ? (I didn't find it).

Thanks