Your browser (Internet Explorer 6) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.

Common Questions: Books on Writing JavaScript for Alfresco

Writing JavaScript for Alfresco

As a leading Alfresco partner, we receive a lot of questions on best practices for implementation and usage of the platform. We will begin sharing this ECM knowledge through a series entitled Common Questions. In this installment, we look at a question we received about the best books and resources around writing JavaScript for Alfresco. If you have any questions, feel free to contact us today.

Alfresco 3 Cookbook – Writing JavaScript for Alfresco
Alfresco 3 Cookbook – Snig Bhaumik


Do you have any recommendation on JavaScript books for Alfresco? We found Alfresco 3 Cookbook online and would like to know if there is a more recent version or of any resources you have around writing JavaScript for Alfresco.


Unfortunately, the Alfresco 3 Cookbook has not been updated in a long time. While you may find some great material in there, your mileage may vary.

Packt recently released a new version of the Alfresco Developer Guide as Bindu Wavell, our Chief Architect, is a technical reviewer. The new version can be found here.

Alfresco Development Tutorial – Writing JavaScript for Alfresco
Alfresco Development Tutorial – Jeff Potts

The current updates to this book include several recipe-style, step-by-step sections to quickly get things done. This is a go-to book for Alfresco development, but the current edition is old enough that some key things—like how to create an extension project—have changed significantly. A lot of this information comes from Jeff Potts’ Alfresco Development Tutorial series. He has done a great job of keeping this series up to date.

Another book from Packt that talks about writing JavaScript and Java for WebScripts can be seen here. It’s quite a bit newer than the previous one and is focused on WebScripts rather than covering more general topics.

You can also view Bindu’s Alfresco Summit presentation where he talks about creating JavaScript administration scripts.

Another great new resource is the Alfresco community site. This is a Jive platform site that has all the old forum and wiki content, but also a lot of activity from the community. It’s a great place to ask development questions and get answers from true rockstars in the community.

Finally, we would be remiss if we didn’t mention that the developer documentation at Alfresco has improved drastically over the past year and a half. You may find some good info here.

Alfresco Developer Help: Simplifying Alfresco Extension Development

Simplifying Extension Development in the Yeoman Generator

In this blog post, Bindu Wavell discusses how to create a project structure in the Yeoman generator that is appropriate for customized Alfresco implementations. This drastically reduces the need to search for and copy/paste data in multiple locations. This new alf-dev-helper project focus on reducing clicks in the UI when working on development tasks—eventually, we expect other types of helpers to be added.

Simplifying Alfresco Extension Development

Bindu Wavell, Chief Architect at Zia Consulting

As you may know, Zia Consulting has been working on an open-source Alfresco Yeoman generator that allows for Alfresco extension project scaffolding based on the Alfresco all-in-one archetype

This project also includes some wizards for adding common extensions such as actions, behaviors, models, and web scripts to your project. Additionally, it has helpers for adding AMP files to your project. One of these helpers is alfresco:amp-add-common. Based on which version of the SDK you are using, and if you are targeting Community or Enterprise, this will offer you a list of third-party AMPs that can be added to your project (multi-selection is possible).

In order to do this, the generator relies on these modules being published to a public Maven repository such as Maven Central or Alfresco Artifacts. Initially, the only two AMPs available from one of these repositories were Support Tools for Enterprise installs and Uploader Plus.

We have been advocating in the community for folks to start publishing their AMPs to a public Maven repository. At BeeCon 2016 we had a good discussion with Florian Maul, the author of the awesome JavaScript Console add-on. He went through the process of getting his AMPs pushed to Maven Central and published a how-to article.

There are now a growing number of high-value AMPs available via one of the public Maven repositories. These include common modules such as:

  • Alfresco Office Services (AOS)
  • JavaScript Console
  • Records Management (RM)
  • Support Tools
  • Uploader Plus

In addition, we have recently seen some more specialized projects pushing their AMPs to a public repository, these include:

  • JavaMelody
  • JScript Extensions
  • Share Inbound Calendar Invites
  • Share Site Announcements
  • Share Site Creators
  • Share Site Space Templates

The alfresco:amp-add-common sub-generator supports adding any/all of these to your Yeoman generated projects with a single command.

For years I have felt it should be possible for developers to jump from any node in a document library view directly to the node browser. This is a very simple customization and I finally got around to coding this up in a reusable project. The project is called alfresco-dev-helper and is now also published to Maven Central and has been added to the alfresco:amp-add-common subgenerator.

Besides the new open in node browser document library action, this add-on enables the execute script action that is provided out-of-the-box, but disabled by default. It also exposes the change type action on the browse screens.

Simplifying Extension Development – Exposed Document Library Actions
Exposed Document Library Actions

My plan for this project is to include simple extensions to the platform and share those that will be most useful for developers. I would not expect this module to be deployed to production.

In summary, we are continuing to make progress on the Yeoman generator for Alfresco. Recently, we have been making it easier to quickly add some useful AMPs and have started work on a sister project to the Yeoman generator where some helpful developer tools that run inside the platform and share will be made available to you.

Bindu Wavel, Chief Architect at Zia Consulting

Bindu Wavell is the Chief Architect at Zia Consulting. He has been involved in enterprise system integration consulting for the past 24 years. At Zia, Bindu provides guidance and mentoring around enterprise content management architecture and design in addition to working hands-on with customers to deliver high-value solutions. Bindu has been working on enterprise content management engagements for the past 10 years. Previously he worked at eConvergent and Aspect Communications focusing on customer relationship management systems. Bindu is passionate about tea and quite interested in hobby robotics and automation.

Ephesoft: Four Features of Practical Innovation

By Jake Karnes, ECM Consultant at Zia Consulting

With an eye to the future, Ephesoft continues to deliver practical innovation which improves the capabilities and usability of its core platform, Ephesoft Transact. Ephesoft demonstrates this commitment to current and future customers with four new features: cross-section extraction, automatic data conversion, paragraph extraction, and automatic regular expression suggestions and creations.

Ephesoft INNOVATE 2016 brought together leading minds to discuss the latest industry advances. Software companies face the persistent challenge of delivering practical innovation while staying true to their product’s role in a customer’s organization. Ephesoft tackles this problem with a two-pronged approach. Ephesoft remains on the cutting edge of document capture technology with their new big data analytics platform—Ephesoft Insight. Insight promises to extract content and meaning from documents scattered across an organization using machine learning and patented text-based analysis. In addition to pushing the envelope with Insight, Ephesoft is continuing to expand and strengthen Ephesoft Transact.

Feature 1: Cross-Section Extraction

Ephesoft Transact, formerly Ephesoft Enterprise, adds several powerful features in the upcoming 4.1 release with roots in customer feedback and provide out-of-the-box functionality which previously required customization. One such feature is cross-section extraction. This technique uses the intersection of two keys to find the correct value. In the example below, the two keys are “Services Borrower Did Not Shop For” and “Borrower-Paid” which meet at the value “$236.55.” This triangulation using multiple keys allows for the extraction of values which are ill-suited for existing extraction methods such as table extraction.


Feature 2: Automatic Data Conversion

Another feature which comes from business use cases is automatic data conversion. This feature allows extracted dates and other values to be automatically normalized to a standard format. For example, a date extracted as “MAR 21 2016” can automatically be converted to “03/15/2016” and vice versa. Other possible data conversions include predefined suffixes and prefixes, data replacement, upper or lower case conversion, and more. One novel use for this functionality would be to clean up imperfect OCR results. The extraction rules could be defined to allow for missing or erroneous characters, and the values could then be corrected during this data conversion step by removing or substituting the known, correct character(s).


Feature 3: Automatic Regular Expression Suggestion and Creation

Another example of Ephesoft’s dedication to improving user experience by expanding Transact’s functionality is the new, automatic regular expression suggestion and creation. Ephesoft has recognized the pain of writing regular expressions by hand, and helps minimize these efforts by suggesting regular expressions automatically. These suggestions are sourced from Ephesoft’s own library of common regular expressions, such as emails, dollar amounts, and dates. But Ephesoft can even help you create custom regular expressions based on the examples provided during extraction training. This strikes a powerful balance between the flexibility to write your own and the ease of having them automatically suggested or created for you. The usefulness of regular expressions is now unlocked without burdening the user with learning the complex regular expression notation. As an added bonus, this feature is already included in the latest release of Transact, and further information can be found at Ephesoft’s wiki page here or in a video demonstration below.

Feature 4: Paragraph Extraction

Paragraph extraction demonstrates Ephesoft Transact capabilities of mining valuable information from unstructured documents. This features enables the user to define values to be extracted from within larger bodies of text, without specific keywords or fixed locations. As an example, consider the following sections of a mortgage note:

Paragraph extraction can be used to extract each of the highlighted values. Even values which wrap around multiple lines (e.g. “Super Mortgage Inc”) can be handled with ease. Previously, this would have required custom scripting or a complex combination of different extraction techniques. Paragraph extraction allows the user to unlock information from their documents which may have been unused before.

These features indicate that Ephesoft’s innovation is not limited to their groundbreaking analytics platform. They continue to implement practical innovation which is equally important for new and existing customers. These features provide straightforward solutions to common pain points. By inviting and accepting feedback from their customers and partners, Ephesoft is pushing the capture industry forward on multiple fronts.


Jake Karnes – ECM Consultant Zia ConsultingJake Karnes is an ECM Consultant at Zia Consulting. He extends and integrates Ephesoft and Alfresco to create complete content solutions. In addition to client integrations, Jake has helped create Zia stand-alone solutions such as mobile applications, mortgage automation, and analytic tools. He’s always eager to discuss software to the finest details, you can find Jake on LinkedIn.

Tech Post: Extracting Metadata in Alfresco

Extracting Metadata in Alfresco

by Jeff Rosler, Solutions Architect at Zia

When importing files, each is uploaded with additional information including things like title, description, and text. Out of the box, Alfresco extracts the properties that have been mapped and metadata is taken from the content using Apache Tika. The TikaAutoMetadataExtracter class loads the supported mime types so all users have to do is create a bean that references that class and then set the properties desired in extraction.

The following are some simple samples for how metadata can be pulled from different mime types and set to Alfresco properties. Since Apache Tika is used as a basic metadata extractor in Alfresco, you can use that to extract metadata for all the mime types that it supports. The current version of Tika that Alfresco is using (for Alfresco and 5.1) is basically Tika 1.6 which supports the following file types. The TikaAutoMetadataExtracter class loads all the mime types that embedded version of Tika supports. So, all you need to do is to create a spring bean that references that class and set the properties to extract and set the Alfresco properties you’d like to have set. You don’t have to write any custom code.

Example 0 – Set logging to see what metadata can be extracted

Before defining your metadata extraction, it’s good to set your logging level for metadata extraction to DEBUG. When you do this, the extracted metadata for a file is shown in the log. This lets you correctly choose the embedded metadata property names to configure. You can set this by going to your file for the repo (alfresco) and adding the following line.

Restart alfresco and import a file. You should see something like this in the log. You can see properties with name spaces such as dc:title (the dc stands for dublin core, a metadata standard) as well as other properties that don’t contain a namespace. You can use these embedded properties to map to standard or custom Alfresco properties.

2016-02-03 10:03:49,474 DEBUG [content.metadata.AbstractMappingMetadataExtracter]
 [http-bio-8080-exec-10] Extracted Metadata from ContentAccessor[ 
 size=286436, encoding=UTF-8, locale=en_US]
 Found: {date=2016-01-22T18:59:00Z, Total-Time=1, extended-properties:AppVersion=14.0000,
 meta:paragraph-count=12, subject=beer, ipsum, meta:print-date=2016-01-22T18:59:00Z,
 Word-Count=405, meta:line-count=45, Manager=null, Template=Normal.dotm, Paragraph-Count=12,
 meta:character-count-with-spaces=2246, dc:title=Tom's Ipsum Beer, modified=2016-01-22T18:59:00Z,
 meta:author=Jeff Rosler, meta:creation-date=2015-12-31T15:49:00Z,
 Last-Printed=2016-01-22T18:59:00Z, extended-properties:Application=Microsoft Macintosh Word,
 author=Jeff Rosler, created=2015-12-31T15:49:00Z, Creation-Date=2015-12-31T15:49:00Z,
 Character-Count-With-Spaces=2246, Last-Author=Jeff Rosler, Character Count=1853, Page-Count=2,
 Application-Version=14.0000, extended-properties:Template=Normal.dotm, Author=Jeff Rosler,
 publisher=Zia Consulting, meta:page-count=2, cp:revision=4,
 Keywords=beer, ipsum, meta:word-count=405,
 dc:creator=Jeff Rosler, extended-properties:Company=Zia Consulting,
 description=beer, ipsum, dcterms:created=2015-12-31T15:49:00Z,
 Last-Modified=2016-01-22T18:59:00Z, dcterms:modified=2016-01-22T18:59:00Z,
 title=Tom's Ipsum Beer, Last-Save-Date=2016-01-22T18:59:00Z, meta:character-count=1853,
 Line-Count=45, meta:save-date=2016-01-22T18:59:00Z, Application-Name=Microsoft Macintosh Word,
 extended-properties:TotalTime=1, extended-properties:Manager=null,
 creator=Jeff Rosler, comments=null, dc:subject=beer, ipsum, meta:last-author=Jeff Rosler,
 xmpTPg:NPages=2, Revision-Number=4, meta:keyword=beer, ipsum, dc:publisher=Zia Consulting}

Example 1 – Set author, title, description

Specify your spring bean. You can name the id anything you want (that is a legitimate XML id) and point to the TikaAutoMetadataExtracter class (yes I know, that isn’t the way you spell Extractor, but the code has misspelled Extractor with an “e” instead of an “o”). In the code block below, we are overriding the default mapping and pointing to a separate property file. The properties could have been listed inline here, but pointing to the property files allows for easier editing.


<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns=""

   <bean id="" class="org.alfresco.repo.content.metadata.TikaAutoMetadataExtracter" parent="baseMetadataExtracter">
         <ref bean="tikaConfig"/>
      <property name="inheritDefaultMapping">
      <property name="mappingProperties">
         <bean class="org.springframework.beans.factory.config.PropertiesFactoryBean">
            <property name="location">


After specifying your spring bean that points to a properties file (e.g., within the properties file, set any Alfresco namespaces you’re specifying for the content model and then each property to be mapped. Note that during the extraction if you specify properties on aspects, those aspects will be applied to the content node automatically for you. Note that you put the embedded metadata property name on the left of the equal sign and the Alfresco property on the right. If you are specifying an embedded property that has a namespace prefix (e.g. dc:title) remember to escape the colon with a backslash (e.g. dc\:title). You don’t need to do that on the property value, just the property.


# Namespaces
# Mappings

Example 2 – Setting multiple Alfresco properties 

Embedded Metadata can be mapped to multiple Alfresco properties by specifying those properties as comma separated values. The example below shows setting the embedded author value to both cm:author and cm:description.


# Namespaces
# Mappings

Example 3 – Specifying when properties are extracted

The Metadata extractor has something called an OverwritePolicy. The OverwritePolicy specifies when an Alfresco property is overwritten. For example, you might not want your extractor to overwrite every time a new version is stored of a file as this would overwrite any of the mapped property values that were updated manually via Share or automatically through actions, workflows or other processes. Therefore, Alfresco defaults the OverwritePolicy to PRAGMATIC. This basically sets it to extract if the extracted property is not null  and the Alfresco property is not set or is empty.

However, if you want to change the behavior so that the extraction happens all the time (e.g. when content is updated), then you should set the OverwritePolicy to EAGER. This can be done by passing that as a parameter within your extractor bean as can be seen below.

<bean id="" class="org.alfresco.repo.content.metadata.TikaAutoMetadataExtracter" parent="baseMetadataExtracter">
      <ref bean="tikaConfig"/>
   <property name="inheritDefaultMapping">
   <property name="overwritePolicy">
   <property name="mappingProperties">
      <bean class="org.springframework.beans.factory.config.PropertiesFactoryBean">
         <property name="location">

Example 4 – Setting tags

Support for mapping tags was added in Alfresco 4.2.c. Details are mentioned in this blog post. You can easily add that to your extraction mapping. It just needs to be enabled in the extract-metadata bean and then the mapping set within your properties file.

NOTE: When setting tags, don’t do this while running from the Alfresco SDK using springloaded. Tagging won’t work and as soon as you try and import some content with tags (after you’ve made the updates below), your content will fail to load.

ALSO NOTE: I noticed in Alfresco 5.0 that the embedded keywords are getting concatenated into a single comma separated tag. This has been identified as a bug and a JIRA (MNT-15497) was created for fixing it. The fix was put in 5.0.4 and 5.1.1.

The following code block can be added to your spring bean xml config file to enable tagging.


    Override metadata extraction bean from action-services-context.xml to turn on the taggingService and enableStringTagging
    This will allow keywords to get mapped to tags.
<bean id="extract-metadata" class="org.alfresco.repo.action.executer.ContentMetadataExtracter" parent="action-executer">
  <property name="nodeService">
    <ref bean="NodeService" />
  <property name="contentService">
    <ref bean="ContentService" />
  <property name="dictionaryService">
    <ref bean="dictionaryService" />
  <property name="taggingService">
      <ref bean="TaggingService" />
  <property name="metadataExtracterRegistry">
    <ref bean="metadataExtracterRegistry" />
  <property name="applicableTypes">
  <property name="carryAspectProperties">
  <property name="enableStringTagging">

After tagging is enabled, just update your property file to map the appropriate embedded Keywords property to cm:taggable. The example below uses the embedded Keywords property.

# Namespaces
# Mappings


Metadata and Alfresco by Jeff Rosler, Solutions ArchitectJeff Rosler has more than 15 years’ experience architecting and developing enterprise content management solutions for customers across multiple verticals to help solve different business challenges. These solutions include digital asset management, component content management using XML, business process management, and web content management utilizing Alfresco and related standards, technologies, and products.

Webinar Series: Insurance in 2016 – Process Efficiency and Data Security

As we move into 2016, many insurance organizations are looking to transition from their end-of-year strategic planning towards the achievement of their set goals. Whether property and casualty, life insurance, reinsurance, or any other type, top priorities are improving process efficiency to deliver measurable business results and enhancing data security to mitigate enterprise risk. But, how can you get there? Our three-part webinar series shows how leveraging automation technologies can deliver a rapid ROI in document processing and also provide your organization with our Universal Content Security. Each webinar is 30 minutes in length and includes a demonstration and specific customer examples.

Webinar 1: Automating Claims Processing 
See how a leading insurance provider revolutionized their business using Intelligent Document Capture and a modern, integrated ECM content hub.

Watch Now!

Webinar 2: Automating Contracts and AP 
Learn to automate common back office business processes —from contracts management to AP—with tools like Document Assembly and enterprise integration into ERP systems such as SAP or Microsoft Dynamics.

Watch Now!

Webinar 3: Addressing Cyber Security
Discover how the application of data security can be automated across the entire organization and extended to external collaboration tools from email to Dropbox.

Watch Now!

Zia Lightning Talks: Alfresco Email Templates

Zia conducts monthly, internal lightning talk sessions. These short, five-minutes presentations cover topics important to Zia, our partners, and the industry. We’ve decided to start sharing some of these useful presentations with you. This post covers the talk presented by Lucas Patingre, ECM Architect at Zia Consulting.

Despite some companies trying to shut down internal emails, they are still frequently used as a notification tool. Right out-of-the box, Alfresco gives us the ability to send inline emails—written directly in the code—in both html and text formats, or to send the emails based on templates.

Benefits of Alfresco Templates

  • Separation of the view
    • Separating the presentation layer from the code makes it easier to work on the email structure or the dynamic content independently.
    • In the end, this will allow us to write and maintain more complex emais.
  • Localization
    • Alfresco supports multiple languages which manifests at several levels. The most obvious is the UI where all text is encapsulated within localized properties files to render based on user preferences.
    • For email templates, we can create one template file per language we want to support and then choose the right one at the time we send the email.
  • Edit online
    • The email templates are stored in the repository making it simple for an administrator to edit them without creating a new build of a customization.

How-To Use Alfresco Templates

  • Calling the action
    • Instead of passing raw text to the email action, you will pass the reference to a template node and a parameter map with the data to inject.


Action mail = actionService.createAction(MailActionExecuter.NAME);
mail.setParameterValue(MailActionExecuter.PARAM_SUBJECT, "Inline email subject");
mail.setParameterValue(MailActionExecuter.PARAM_TEXT, "Inline email body");


Map<String, Object> model = new HashMap<String, Object>();
Action mail = actionService.createAction(MailActionExecuter.NAME);
mail.setParameterValue(MailActionExecuter.PARAM_SUBJECT, "Templated email subject");
mail.setParameterValue(MailActionExecuter.PARAM_TEMPLATE, getEmailTemplate());
mail.setParameterValue(MailActionExecuter.PARAM_TEMPLATE_MODEL, (Serializable) model);
  • Bootstrapping the email templates
    • While not mandatory, it’s better to bootstrap the templates to the repository instead of uploading them manually. You should end up with one template per language you want to support, similar to this:


Note: The configuration used to bootstrap the templates is out of the scope of this blog post. You can find reliable resources online on how to bootstrap using the ImporterModuleComponent.

  • Localized email template fetching: getLocalizedSibling
      • The FileFolderService has an interesting method called getLocalizedSibling that can retrieve a localized (using the server’s locale) version of the template.
private NodeRef getEmailTemplate() {
    try {
        List<NodeRef> nodeRefs = searchService.selectNodes(
                nodeService.getRootNode(StoreRef.STORE_REF_WORKSPACE_SPACESSTORE), EMAIL_TEMPLATE_XPATH, null,
                nameSpaceService, false);
        if (nodeRefs.size() != 1) {
            logger.error("Cannot find the saved search notification email template: " + EMAIL_TEMPLATE_XPATH);
            return null;
        return fileFolderService.getLocalizedSibling(nodeRefs.get(0));
    } catch (SearcherException e) {
        logger.error("Cannot find the saved search notification email template: " + EMAIL_TEMPLATE_XPATH, e);
    return null;

Capabilities of FTL Templates

  • Basic variable injection
    • This is extracted from the default “Following” email template in Alfresco
    <#assign followerFullName>${followerFirstName} ${followerLastName}</#assign>
                    <img src="${shareUrl}/res/components/images/help-people-bw-64.png" />
                    <div>${(followerFullName?trim)?html} is now following you.</div>
                    <div><#if followerJobTitle??>${followerJobTitle?html}<br/></#if></div>
  • Freemarker logic
    • This is extracted from the default “Activities” email template in Alfresco. As activities can be one of several kinds and we want to format the notification differently for each kind, it requires more ftl logic. I have remove much of the actual display work to mainly keep the logic structures.
    <#if activities?exists && activities?size > 0>
        <#list activities as activity>
            <#if activity.siteNetwork??>
                <#assign firstVar="Something">
                <#assign otherVar=false>
                <#switch activity.activityType>
                    <#case "">
                    <#case "">
                        <#assign firstVar="Something else">
                    <#case "">
                        <#assign otherVar=true>
                <div class="activity">
                    <#if otherVar>${firstVar}<#else>Not var</#if>
  • Handle nodes
    • Another useful is the ability to fetch nodes and access their different properties. To use this, you will need to inject “companyhome” in your email template.
        <th>Modified date</th>
    <#list savedSearch.getNewResults() as savedSearchResult>
        <#assign savedSearchResultNode=companyhome.nodeByReference[savedSearchResult.toString()]>
            <td><a href="${shareUrl}/page/user/${}/profile">${}</a></td>
            <td><a href="${viewUrl}${['sys:node-uuid']}">${}</a></td>

From this, you can see the benefits of utilizing these templates to create a more streamlined deployment of your email communications. If you have any questions on how to best implement this approach, please contact us today.

Our Thoughts on the All-New Ephesoft Universe

Ephesoft UniverseToday the industry received word of an innovative new technology—Ephesoft Universe. Universe is a tool that matches enterprise Big Data with intelligent capture, allowing you to process and analyze all of the content contained in your organization’s documents, even if unstructured. I have had the pleasure of early access to the product for evaluation and want to share my thoughts with you. 

Universe allows business users to define different documents and data they would like to analyze in an easy and intuitive fashion. By automatically identifying large amounts of data fields like addresses, amounts, etc., users can tag the values with appropriate names used in the business (e.g., primary address, loan amount, SSN, employer). Universe then analyzes the values and determines the best ways to extract the data as more documents are processed. Once the definitions are set up, very large groups of documents can be processed in a very short time by utilizing Apache Spark clusters. This can be deployed on premise or in the cloud.  

It’s all well and good to rattle off some technical specs and usage but why should you, and I, care? While Ephesoft at Innovate 2015Ephesoft Enterprise for intelligent capture allows you to automate the intake of documents to drive business process and archival, it doesn’t harness the immense amount of data you already have in your enterprise. Imagine, as a mortgage insurance company, being able to set rates based on data you already have from the many closing packages you have processed. With Universe, this data is found by looking at defaults in various zip codes, size of homes, loan amounts, home values, and more. You can even look at the data you have and project it out for months. Consider a fraud detection company having the ability to determine how many loan applications a particular name or social security number has applied for in a specified amount of time. Many companies pay other entities for this information—data that already exists in documents they process in their enterprise.

We are excited about this innovative technology and the advanced solutions it will enable Zia to provide to our clients. Ephesoft Universe is going to save our customers time and money while lowering risk. Please contact us to discuss how this technology can help you.

– Pat Myers, EVP and Co-Founder of Zia Consulting

Demo – Adhere for Alfresco: Legal – Part 2

In this video, Sr. Solutions Engineer Jon Solove demonstrates the execution of a contract using Adhere for Alfresco: Legal, a content management solution from Zia Consulting.

For corporate legal departments within many organizations, the choice of a document management system has been limited to a small number of legacy vendors with complex and costly offerings that users are forced to accept, rather than working the way they want to work. The result is “ECM avoidance” with users finding ways around their ECM system–utilizing email, shared drives, or cloud technologies.

Today there is an alternative: Adhere for Alfresco: Legal, powered by Alfresco and delivered by Zia Consulting. Zia understands that when systems are easy-to-use and leverage existing tools like Office or Google Docs, the result is increased utilization and an improvement in control and compliance. Our Adhere for Alfresco: Legal solution delivers document and records management that’s as simple as using email or file systems, with the power of enterprise-class CMS features and functionality.


Video Demo – Adhere for Alfresco: Legal – Part 1

In this demo, Sr. Solutions Engineer Jon Solove demonstrates the creation of a case using Adhere for Alfresco: Legal, a content management solution from Zia Consulting.

For many corporate legal departments and AM100 law firms, the choice of a document management system has often been limited to a small number of legacy vendors with complex and costly offerings that users are forced to accept, rather than working the way they want to work. The result is “ECM avoidance” with users finding ways around their ECM system–utilizing email, shared drives, or cloud technologies.

Today there is an alternative: Adhere for Alfresco: Legal, powered by Alfresco and delivered by Zia Consulting. Zia understands that when systems are easy-to-use and leverage existing tools like Office or Google Docs, the result is increased utilization and an improvement in control and compliance. Our Adhere for Alfresco: Legal solution delivers document and records management that’s as simple as using email or file systems, with the power of enterprise-class CMS features and functionality.

From the Desk of Yoran: The ROI from Data-Centric Security

This is the second blog post in the series “From the Desk of Yoran”.

CovertixYoran Sirkis, CEO of Covertix, is a seasoned executive with more than 20 years of experience in information security, specializing in data and physical risk management. He is also a frequent speaker at leading industry conferences.


The ROI from Data-Centric Security

When was the last time you counted the number of security tools in your organization? How many different vendors are involved? What are the maintenance and licensing costs?

I bet you lost count… anyone would.

Companies strive to define and apply security rules that will best protect data, based on their specific business needs. During that process, IT staff encounter evolving security needs and are exposed to an endless amount of solutions—each addressing a valid, real-world security challenge.

As a part of the process of protecting their enterprise data, organizations end up dealing with a variety of vendors, pricey integrations, busy helpdesks, frustrated users and, continuously increasing expenses.

Doing More with Less

As I mentioned in my previous post, The Need for Data-Centric Security, the age of data-centric security transforms the security focus from top-down to bottom-up. It’s this reasoning that makes a data-centric solution more valuable than what it was originally implemented for.

Guided by the understanding and importance of offering a security solution that presents a clear ROI, we have developed a single data-centric solution that delivers much more than file protection.

Data Classification

How many unstructured data files do you think sit on your corporate network? Take a guess. It’s a scary thought, isn’t it? Before you make your team (and yourself) insane by protecting every single file individually, we recommend you take the data classification approach—that’s right, data-centric.

You need a system that easily lets you implement policies across data document types, such as CAD design files from R&D, to files in the accounting department that contain the number 4128 at the start of a 16-digit number.

File Protection 

Having a file protection solution in your organization is critical, but most solutions provide limited protection. A data-centric security solution brings much more to the table. It enables organizations to protect, manage, and audit files internally AND externally, to share sensitive information with external users, and to protect information on different devices.

File Encryption

Encrypting files is necessary to ensure your data is protected and is used only by the people it was intended for. Most solutions burden users, forcing them to learn a new system and placing all the responsibility on them.

A data-centric solution removes that burden by offering a system that operates seamlessly and without affecting users’ behavior. This secures your data in all of the following cases:

  • After the file has been opened (using any device or location)
  • When content is copied/pasted to a new document
  • Protection of the file’s metadata
  • When sensitive files are shared with external users

Your files are protected, and you can audit and monitor the usage of their content no matter where the files actually reside—inside or outside the organization.

Secure Vaults

Confidential data is often placed within secure vaults. But even the best vaults will only keep your data secure when it is stored within it. A data-centric solution provides persistent security, keeping your data secure anytime and anywhere. From the moment a confidential document is created, through any transport, and even when it is download on any device.

As it is transparently integrated into existing business driven processes with automated rules or manual override, a data-centric security solution will not impose on IT staff and is not dependent on a user’s actions.

Cloud Security

It’s a given that assets residing in the cloud need to be protected. Because of this, cloud providers began offering their own security solutions as well as those from third parties. Of course, the costs begin to pile up and companies are often still uncertain about who else might have access to their cloud-based data.

Deploying a smart, data-centric security solution is the best way to protect your data anywhere—and even from cloud providers themselves.

Data Leak Prevention (DLP)

DLP solutions aim to prevent files from leaving the your business unintentionally or through malicious actions. But how do you protect your data if it is leaked? A data-centric security solution continues to monitor your files even outside the organization and ensures the data they contain remains secure.

And most importantly….

While plenty of solutions secure your data at rest, or in motion, or when it goes to third parties, but only a data-centric solution can secure the file structure and the data it contains so you know that data is always protected.

If you have concerns about your confidential data when it’s in motion, at rest, or in use; and whether it could be lost through a data breach, from a stolen device, or other unintentional or malicious way,  we can give you peace of mind. You CAN have a system with a strong ROI, because you won’t find yourself facing lawsuits or losing customers and your reputation.

For more information, please visit