Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
fh-wfm-workflow-angular
Advanced tools
An Angular 1 Implementation of the fh-wfm-workflow module
This module is an Angular JS implementation of Workflows for the Raincatcher project.
This module is packaged in a CommonJS format, exporting the name of the Angular namespace. The module can be included in an angular.js as follows:
var config = {
mode: 'admin',
listColumnViewId: 'listColumnView',
mainColumnViewId: 'detailColumnView'
};
angular.module('app', [
...
, require('fh-wfm-workflow-angular')(config)
...
])
The following configuration options are available for this module:
Allows to switch between user based views and admin views. Possible values 'admin' or 'user'
This is the identifier for the Angular view where the main Workflow views will be rendered.
This is the identifier for the Angular view where the list of Workflows will be rendered into.
This is useful for organising where the lists will be rendered on-screen.
If not specified, the lists will be rendered into the mainColumnViewId
.
This is only used for the admin
mode of the module.
This is the identifier of the Angular view where the progress of a workflow is displayed to the user. This is only required for scenarios where a workflow is being progressed (e.g. in a mobile application)
Name | Description |
---|---|
workflow-detail | Displays the workflow to the user and allows re-ordering of the steps. |
workflow-form | Allows editing of the workflow name |
workflow-list | Displays a list of workflows |
workflow-progress | Displays the current progress of a workflow |
workflow-result | Displays the result of a single workflow |
workflow-step-detail | Displays the detail for a single step of a workflow |
workflow-step-form | Allows the user to edit a single step of the workflow |
The following directives are used to guide a user through the steps necessary to complete a workflow. The workflow module itself does not contain the logic required for each step, but uses the template directives to render each of the steps to the user.
The workflow-process-parent
route is an Angular JS abstract route that is used for all steps in a workflow.
The workflow-process-begin
route and controller are used to display the summary of the workflow and any results that there may be.
The workflow-process-steps
route publishes topics to get the current state of the workflow for a workorder.
Based on the state, the workflow-step
directive renders the template defined in the workflow step.
At this point, control is passed to the module that implements the individual step.
As part of rendering Workflows, this module publishes and subscribes to several topics. These topics can be implemented in your application or you can use the fh-wfm-workflow module that already has implementations for these topics.
Each of the following topics subscribes to the error
and done
topics.
If the parameter includes a topicUid
, the error topic should have the topicUid
appended to the done
or error
topic.
Topic | Parameters |
---|---|
wfm:workflows:list | NONE |
wfm:workflows:read | {id: "IDOFWORKFLOW", topicUID: "IDOFWORKFLOW"} |
wfm:workflows:create | { workflowToCreate: workflowToCreate, topicUid: topicUid} |
wfm:workflows:update | { workflowToUpdate: workflowToCreate, topicUid: topicUid} |
wfm:workflows:remove | { id: "IDOFWORKFLOW, topicUid: "IDOFWORKFLOW"} |
wfm:workorders:list | NONE |
The following topics allow the updating of the workflow state to progress through a workflow.
Each of the done
topics for the following topics contin the following parameters
{
workflow: {
//The details of the current workflow being progressed
},
workorder: {
//The details of the current workorder being progressed
},
result: {
//The current result object for this workorder being progressed
},
nextStepIndex: 0 //The index of the next step to display
step: {
//The details of the step to display
}
}
Topic | Parameters |
---|---|
wfm:workflows:step:begin | {workorderId: "WORKORDERID", topicUid: "WORKORDERID"} |
wfm:workflows:step:summary | {workorderId: "WORKORDERID", topicUid: "WORKORDERID"} |
wfm:workflows:step:previous | {workorderId: "WORKORDERID", topicUid: "WORKORDERID"} |
wfm:workflows:step:complete | {workorderId: "WORKORDERID", topicUid: "WORKORDERID", submission: {...}, stepCode: "CODEOFCOMPLETEDSTEP"} |
Install module dependencies
npm install
Link module into your app
npm link .
Start monitor changes in templates.
grunt wfmTemplate:watch
FAQs
An Angular 1 Implementation of the fh-wfm-workflow module
We found that fh-wfm-workflow-angular demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.