WoodWing’s Smart Mover v10.4.1 – New Features

Screenshot 2020 04 16 11 35 50

In following up on the recent updates to Smart Mover (see v10.4 features here) I have listed the latest features to the product below. One of the new features was requested by a customer just last month and that is the ability to ‘Auto connect to service’. The Smart Mover service can, of course, be started up when the machine reboots. This feature allows the Manager to also come up if you need it to.

Smart Mover v10.4.1 was released on April 9th, 2020. It includes the following: 

  • Smart Mover Manager can now export Log file detail. Open the Log then select All or the entries you want and click export. Errors or warnings are indicated by an exclamation mark in first column.
  • The Preferences > Logs window includes the option to download the HTTP Logs from the Smart Mover Service machine to the Smart Mover Manager machine desktop. You can also Clear the Logs. This was done to eliminate the need to access the Smart Mover Service machine directly.
  • The Preferences >Misc window includes 2 options that are invoked when Smart Mover Manager is launched: “Open Connect Window to Service” and “Auto Connect to Service”. The first one simply opens the Connect window where you can enter the password and connect. The second will automatically connect to Smart Mover Service if the password has also been provided.
  • When setting up various Tasks the “select folder dialog” now includes the option to Upload files into the selected folder. You can now also Delete files or folders. This was done to eliminate the need to access the Smart Mover Service machine directly. The upload option should be used for scripts, templates and other supporting files and not for production files like images, layouts, and so on.
  • Image File Processing IM & SIPS both now allow the command to include data from an associated -metadata.xml file. This is done by entering {/pathToMetadata} in the command.

 

If you have any questions either hit me up here or send a note to ‘sales@woodwing.com’ and we’ll get back to you ASAP.

WoodWing’s Smart Mover v10.4 – New features

Been awhile since my last update and so, because of that, I thought I would start with information about Smart Mover’s latest features. 

Screenshot 2020 04 16 11 35 50

Smart Mover v10.4 was actually released back in November of 2019. It included the following: 

Features

  • Support for MacOS 10.15 (Catalina) has been added.
  • The Copy Files Task now includes the option “Copy Files that have been stable for X seconds”. This option can be used to insure that each file is not still being written to by another application. Background: Before any Task operates on a file it checks to see if another application has the file open. It does this by briefly opening the file with write access. If the file cannot be opened then it is assumed that another app is still writing to it and it is skipped until the next time the Task runs. But there are some situations where this technique may not always work. To work around those times, using this option, the Task first gets a list of all the file sizes that it will be processing. It then waits for the designated number of seconds before it tries to copy each file. If the file size has changed during that delay or the file was not in the original list, it is skipped until the next time the Task is run.
  • Elvis Update Bulk Task added. This Task does the same as the Elvis Mod MetaData except that all the processing is done server side with a single command. The Elvis Mod MetaData runs the desired query and then updates each asset one at a time, logging each update. If you are updating more than a few hundred assets then you should use the Bulk Task. It is much faster but does not provide a detail log of the assets that have been updated. Once completed, the Bulk Task will log how many assets where updated along with the number of errors. No detail is available though.
  • Both Google and AWS Translate Tasks now include the option to “Add Translation Language Code to File Name”. This allows you to translate the same file into multiple languages and place them all into the same folder. So a file named “sometext.txt” translated into Spanish would be named “sometext-es.txt”.
  • Both Google and AWS Translate Tasks can now dynamically translate into languages designated in an associated -metadata.xml file. This is done by picking “-metadata.xml XPath” in the Translation Language pop-up and then providing an XPath valid expression.
  • Example: If I have a custom Enterprise field called “Languages” and a User enters “es” (the code for Spanish) into that field for a particular article, I can then use the Enterprise Download Task including both the “native” and “metadata” for that article. If I enter “//ExtraMetaData/ExtraMetaData[Property=’C_LANGUAGES’]/Values/String” into the XPath field then the article will be translated into Spanish. Additionally, if a comma-delimited list of language codes is provided in that field then the file will be translated into each of those languages. So if I entered “es,de” into the Languages custom field for the article, it would be translated into both Spanish and German. Each Translated file name will include the language code to differentiate them and prevent overwriting.
  • The AWS Translate Task now includes: Hindi, Malay, Norwegian, and Persian.
  • The Enterprise Check Out-In Task now includes the option to set the Status to any given value. This can be done for both the Check-Out and Check-In functions.

 

 

 

If you have any questions either hit me up here or send a note to ‘sales@woodwing.com’ and we’ll get back to you ASAP.

WoodWing’s Elvis DAM has been updated

Elvis DAM version 6.35 has been released!

We’ve got some some nice changes:

  • Pro client: Manually linking files.
  • Elvis REST API try-out page (BETA).
  • Elvis InDesign plug-in: disabling the automatic linking of images when opening a layout.

The first item is a feature that allows you to manually create a relationship between File A and File B by dragging File A onto File B in the client. Note that Elvis auto generates relationships as well such as creating relationships when you create a variant or drag an asset over to a InDesign layout.

The second item is really nice if you are developing an integration between Elvis and a tool like a PIM. Instead of using a tool like ‘Postman’ you can use the try-out page to see if the query is returning the items you are expecting.

See more here.

WoodWing Workflow Automation Tools: Scriba and Smart Mover

WoodWing produces two distinct workflow automation tools: WoodWing Scriba and WoodWing Smart Mover. Each of these tools has its own advantages and use cases. I will use this article to quickly introduce each of the tools. I will follow up with more articles that outline specific use cases and examples of how each tool can be used.

One key thing to note is that while each of these tools has parts that are specific to working with WoodWing’s other systems they are not limited to only working with those tools.

What is WoodWing Scriba?

Scriba Manager

Scriba, at its core, is a rules based workflow engine. A management application is used to take ‘Rules’ and group them together to create a ‘workflow’. The engine will then run the workflows based on some schedule. Workflows can also be triggered by an event coming into Scriba such as a Webhook call to a Scriba endpoint.

Workflows are created, in part, by using ‘connectors’. The connectors help to integrate the workflow engine with other tools (MySQL, InDesign Server, etc) or systems (WoodWing Enterprise, WoodWing Elvis and others). Scriba’s connectors are not limited to just working with WoodWing’s systems. Connectors can be created to talk to ANY system. Naturally WoodWing has a series of connectors available which we’ll discuss in the next post.

Because of the connector concept, one of the biggest advantages of Scriba is that the ‘workflows’ are modular. For instance, let’s say one of the workflows that is created takes content from our Enterprise product, downloads it, does a transform and sends the content to Drupal.

After the work is completed the business decides a year later to move to WordPress. In this case 2/3rds of the workflow is still viable and only the Drupal ‘connector’ needs to be switched out. This mean that a large chunk of the original workflow code is retained and there is far less rework.

What is WoodWing Smart Mover?

Smart Mover Manager

Smart Mover is similar to Scriba in that it acts as a workflow engine. Smart Mover has a ‘engine’ that is configured with a management application. The engine can run on Linux, Windows or Mac OS and the management application can run on Windows or Mac OS.

Smart Mover provides tasks to work with WoodWing Enterprise, WoodWing Elvis and tasks that provide features like uploading to FTP sites, sending email and other features.

Smart Mover implements its functionality through ‘tasks’. One or many Tasks are put together into a ‘Process’ which can be set to run at an interval such as every 5 minutes, once a day, etc. The process is triggered and the tasks within the process do their work.

What’s Next?

In the next article I’ll outline the differences between Smart Mover and Scriba as well as why some customers may choose one over the other…or use both!

Interested in seeing more?

Send us an email at sales@woodwing.com and mention Scriba and/or Smart Mover in your note. We look forward to talking to you.