This release is a pre-release and may not be stable for production use.
This package provides a new portlet for Plone 3 called “Workflow steps”. It can be configured to show:
A custom header
Some lead-in rich text, if desired
The state of the current object, including that state’s full description
All available transitions, optionally with their full descriptions
State and transition descriptions are rendered as HTML. Furthermore, the following special variables may be used.
${portal_url} – The url of the portal (or navigation) root ${object_url} – The url of the current object ${folder_url} – The url of the current folder
The idea is to make it possible to present a list of “next steps” as part of the workflow, including links to edit forms and the like. Changelog =========
1.0b3 (2009-04-15)
Don’t hide the portlet if there are no transitions, but there is state info. [optilude]
1.0b2 (2009-03-31)
Hide the portlet if there’s no state info and no transitions. [optilude]
1.0b1 (2009-03-28)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for collective.portlet.workflowsteps 1.0b3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.portlet.workflowsteps-1.0b3.tar.gz | 12.2 kB | Without provenance | Details for collective.portlet.workflowsteps-1.0b3.tar.gz |
Release files / collective.portlet.workflowsteps-1.0b3.tar.gz
| Download URL | collective.portlet.workflowsteps-1.0b3.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3733a7776971e6ef4d6079b36fc46e237db4294b3255a7bb600c6a216a21f8f1
|
|
BLAKE2b-256 checksum How to use checksums |
79923391d90dace79b0697cbe0472ec79583a9b3452eac12928ccdb3fd7580dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.portlet.workflowsteps 1.0b3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
