Archive for July, 2011

locking models

Posted: 27 July 2011 in Uncategorized

Below is a description of the locking models:

Submit lock => The file can be modified if the user is the owner of the lock in the current workarea or if there is no lock on the file. Users in other workareas can edit their version of the file whilst the file is locked but will not be able to submit it before the file has been submitted. This allows for parallel development on files in parallel workareas.

Optional write lock => The file can be modified if the user is the owner of the lock in the current workarea or if there is no lock on the file. Users in other workareas cannot edit their version of the file whilst the file is locked. This allows parallel development on files that are not locked and forces serialisation of changes on locked files.

Mandatory write lock => the file cannot be written to unless the user has acquired a lock on it in the current workarea. Users in other workareas cannot edit their version of the file whilst the file is locked. This prevents parallel development and forces serialisation of changes on files.

Things to know:

  • The locking model in effect for a user in a branch is the most restrictive locking model between the branch locking model and the least restrictive role locking model of the applicable roles of the user in the branch. Thee submit locking model is teh least restrictive and the mandatory locking model is the most restrictive.
  • The Content Center interface will always attempt to lock a file when modifying it. Note that Content Center is not the only way to edit files. (access to the Y: drive or CSSDK can also modify files)
  • The local files applet can upload files and unlock them.
  • A user can release the file locks it has acquired if its role has the UnlockFiles privilege.
  • A user cannot remove unlock files when he/she is not the lock owner.
  • The workarea owner can unlock files in the workarea, whether it owns the lock or not.
  • User who have the permission override “View and modify files in workareas where they are not a member of the group designated for sharing” can unlock files in the workarea, whether it owns the lock or not.
  • Once a branch has been created, its locking model cannot be changed.

email task custom email

Posted: 6 July 2011 in Uncategorized

If you want to create custom emails, it is fairly easy since it is all using XSL to transform the XML of the job.
the hard part is to figure out what the the original XML to transform is:

create a debug.xsl stylesheet which will do no transformation at all:
<?xml version=”1.0″ encoding=”UTF-8″?>
<xsl:stylesheet xmlns:xsl=”http://www.w3.org/1999/XSL/Transform” version=”1.0″>
<xsl:output method=”xml” />
<xsl:template match=”/”><xsl:copy><xsl:apply-templates /></xsl:copy></xsl:template>
<xsl:template match=”*” name=”elements”><xsl:copy><xsl:apply-templates select=”@*” /><xsl:apply-templates /></xsl:copy></xsl:template>
<xsl:template match=”@*” name=”attributes”><xsl:copy /></xsl:template>
</xsl:stylesheet>

Add a email task to your workflow and customise its mail template property to the file in teamsite. It is a good idea to place them all together so mine is:
/iwadmin/main/config/STAGING/workflow/email/debug.xsl

Run the workflow and check your inbox ; The message contains your xml content. Now all you have to do is create additional templates and you will have your custom emails in no time. What’s more, you can swap between them as you like as they all render the same XML.

check it out: Menendez album launch for ‘apple for teacher’.