More in this section

Forums / Developing with Sitefinity / Turning on workflow approval

Turning on workflow approval

37 posts, 0 answered
  1. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    29 Jan 2009
    Link to this post
    Hello Duncan,

    Straight to your questions:
    1. Q3 SP1 is in the beta, SP2 will be with the official stable release.
    2. The 3.6 beta is not compatible with the 3.5 at the moment. We will fix this for the stable release though. The difference in the backend architecture is too big.
    3. We will release two versions of the 3.6 - one for the .NET2.0 and another for the .NET3.5 platform.

    Kind regards,
    Georgi
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  2. Jen
    Jen avatar
    11 posts
    Registered:
    18 Jan 2009
    01 Feb 2009
    Link to this post
    Once you purchase license(s) - are you given the option to download beta releases, or just the full version + any sps?  (Just curious as I'm still on trial).

    Also excuse my ignorance but why are you releasing a version for 2.0 and 3.5 separately?  Don't they both run off the .NET 2.0 framework?  Or are there specific dlls that have been updated to 3.5?  Just wondering how this will impact us.

    Finally - what is the anticipated release date of the full version of 3.6.  I cannot recommend this package as our preferred CMS with the workflow bug (the create + publish ability) that is in 3.5 as its a key feature we require.  I notice 3.6 is not recommended for production release so obviously don't want to aim to use the beta for a client website :)
  3. Chris
    Chris avatar
    8 posts
    Registered:
    07 Oct 2008
    02 Feb 2009
    Link to this post
    Hi,

    I've taken a look at the 3.6 beta and have found that the 'creator' bug still exists. As a user belonging to a role where I should have rights to create pages but have aprrove and publish rights explicitly denied I can still publish the page and it goes live straight away. I don't even have the option to send it through any form of workflow.

    Technically the fix has been announced as being in version 3.6 and not in the beta of 3.6. Should I see the fix in the beta? What is this new 'special role' you mentioned earlier in this thread and how is it used? I don't notice anything different in terms of the roles between 3.5 and 3.6.

    Thanks,
    Chris.
  4. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    02 Feb 2009
    Link to this post
    Hello Chris,

    The special role which is mentioned earlier is named 'owner'. It has the default rights for the owner of the specified item. You can predefine the owner permissions by changing the 'owner' role rights. Also the owner rights are with higher priority, so even you have explicitly denied them in another role, the creator of the item will still have the owner permissions. This functionality is implemented in the Sitefinity v3.6 Beta. The thing which is omitted in the Beta is that the 'owner' role is missing in the roles dropdown list for the [All Pages] Site Map node, because it does not implement IOwnership interface, but it will be there for the official release. Please let us know if it works differently on your side.

    Regards,
    Georgi
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  5. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    02 Feb 2009
    Link to this post
    Hello Jen,

    Once you purchase license(s) - are you given the option to download beta releases, or just the full version + any sps?  (Just curious as I'm still on trial).

    The download options are just as your at the moment. You can download the beta from http://www.sitefinity.com/download/sitefinity-3-6-beta/Sitefinity_3_6_1836_standard.exe

    Also excuse my ignorance but why are you releasing a version for 2.0 and 3.5 separately?  Don't they both run off the .NET 2.0 framework?  Or are there specific dlls that have been updated to 3.5?  Just wondering how this will impact us.
    The 3.5 version are built with this target, because the Silverlight controls require .net 3.5. Also, starting with 3.6, we are not going to build the future versions with .net2.0 support.

    Finally - what is the anticipated release date of the full version of 3.6.  I cannot recommend this package as our preferred CMS with the workflow bug (the create + publish ability) that is in 3.5 as its a key feature we require.  I notice 3.6 is not recommended for production release so obviously don't want to aim to use the beta for a client website :)

    Of course, the the beta is intended to power a live web site. We confirm that the workflow bug is fixed for 3.6, and we expect this version to be released by the end of this week.

    I will be glad to answer any other questions you might have.

    Greetings,
    Georgi
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  6. Jen
    Jen avatar
    11 posts
    Registered:
    18 Jan 2009
    03 Feb 2009
    Link to this post
    Can I get more information on this Owner role?

    If I have "Bob" who is an editor (and creator) of content - but I don't want him to be able to publish anything live.

    If he creates the page - he'll be considered the Owner of the page ?  In which case I'd want to set the owner without the ability to publish.

    However if I have "Alice" who is the approver of content.  If she was to create a page - she would be considered the Owner and potentially not be able to publish this particular page because Owner permissions take priority over other permissions?

    Or am I confused?? :)

    Thanks,
  7. Vlad
    Vlad avatar
    498 posts
    Registered:
    19 Jun 2017
    03 Feb 2009
    Link to this post
    Hello Jen,

    It's not that. I will try to explain further.
    The priority is applicable only within a single right, and the common user permissions are a union of the permissions of the roles the user belongs to.
    The main rule is that Deny permission for a specific right has a higher priority than Allow permission for the same right, i.e. if you have a role 'Approvers' with Approve right set to Allow and a role 'Editors' with Approve - Deny, the users which are belong to the both roles, won't have Approve permission.
    The 'owner' role is an exception of this rule, its Allow permission is with higher priority than Deny of the other roles.

    As for the scenario you mentioned:
    Lets say that Approve right is not set for the 'owner' role, but you have an 'Approvers' role with Allow Approve. Alice belongs to 'Approvers' role, but Bob - not. If Alice create a page, she will be able to publish it, even she is the creator (which can't Approve), because her actual permissions are a union of the 'owner' and 'Approvers' roles.


    Sincerely yours,
    Vlad
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Register for webinar
37 posts, 0 answered
1 2