Posts tagged "Adobe"

Protecting your Outlook database with Creative Cloud

I use Outlook on my Mac for email and calendaring. While I have access to Office 365 and the web versions of the apps that comprise it, I am more comfortable using the desktop application. In addition, I use email rules to help manage the large volume of messages I receive every day. Since I get a lot of email with a lot of attachments, my Outlook database gets large very quickly. Also, it goes corrupt from time to time. When I rebuild the database, very often my mail rules get confused and they need to be adjusted to point at the appropriate target folders. This is annoying. I decided that I needed to come up with a plan to make it easier to recover from database failure, and this article provides a solution, or at least some security if not a true solution.

Creative Cloud offers desktop file syncing for customers who install the Creative Cloud Desktop app. This works much like Dropbox, in that there is a folder on your computer that the CC Desktop app syncs with your CC folders online. This is a very handy feature for sure. You can learn how to enable desktop file syncing here. You can also share a folder with one or more other Creative Cloud users. In that case, all of the collaborators have access to the same files on their desktop. This is handy if you are working with a team and need to ensure that you all have the most current assets. You can learn how to share a folder with another Creative Cloud user here.

One of the benefits of using CC file sync is that your files are versioned in the cloud, which means that when you replace a file in your synced folder on your computer, the previous version is stored in the Cloud along with your current version. According to the CC Versioning FAQ, The Creative Cloud stores previous versions for 10 days, which is long enough for most users to be able to recover from a disastrous “Save” when you should have chosen “Save As…” Versioning is also our friend when we consider the Outlook database, because if I have previous versions of the database available, then I can roll back to a previous state and get back to work. Unfortunately, Outlook writes to the database frequently, so it is not a good idea to put your Microsoft User Data folder in your Creative Cloud folder. If you do, then CC will try to sync your Outlook database all the time, causing errors on both the CC side and on the Outlook side. A better strategy is to copy the Outlook database to a folder in CC on a schedule.

I use Automator to copy the Database, but it’s not as simple as “copy the Outlook database to my Creative Cloud folder.” Before you copy the database, however, it is best to ensure that Outlook is done with it. The best way to ensure that the database is “at rest” is to quit Outlook. Once Outlook has shut down, then it is safe to copy the database. When the copy is finished, then we need to restart Outlook. At the end, it is polite to send a message that the operation was successful. If you follow this flow, then you will safely have a versioned backup of your Outlook database going back 10 days.

In Automator, I created a workflow and used Calendar to schedule it. It uses the following actions in sequence:

  1. Quit Application: Microsoft Outlook
  2. Get Specified Finder Items: your Outlook Database file (not the enclosing folder)
  3. Copy Finder Items: to a folder in Creative Cloud called Database Backup
  4. Launch Application: Microsoft Outlook
  5. Display Notification Center Alert: Some message to let you know everything was successful

In order to send a Notification Center alert, I used a nifty Automation Action from Automated Workflows, LLC. Read about it and get it here.

The backup Outlook workflow in Automator

The backup Outlook workflow in Automator

If you would like to download the workflow and modify it for your own use, you can download the BackupOutlookDatabase workflow. Unzip the workflow and double click it to install. You will need to modify the workflow in order for it to work properly. Whether you download mine and modify it or make your own, you need to save the workflow and then save it again as an application in order to execute it with iCal.

To save your workflow as an application, you need to expose hidden menu options in Automator. Hold down the Option Key and click the File menu. You will now see Save As… Choose it and then save your workflow as an Application to a place you can find later.

Advanced Options in File Menu

Hold down the Option Key to expose Advanced Options in File Menu

Save as Application

Save as Application

Now, you need to schedule the workflow to run at a convenient time. I used Calendar to schedule the event, since the whole premise here is that the Outlook Database can become corrupt. If we use Calendar, then there is some built-in peace of mind because we’re using another system to backup the system of record. In Calendar, create a new calendar called Automator so you can hide the daily backup events. In the Automator Calendar, create a new event called “Backup Outlook” at a convenient time for you. I chose 2:00 am Eastern Time. Set this event to recur every day with no expiration. Set the action to Open File>Other… and browse to your Automator Workflow Application that you made in the last step.

Det the calendar event properties

Det the calendar event properties

There you have it: an automated backup for your Outlook Database using your Creative Cloud account. It is important to note that your computer needs to be in a state to run the Workflow at the time you designate, so if you have a laptop, you might want to leave it open or on overnight. It’s OK if the computer goes to sleep. The workflow will run so long as the computer isn’t powered down.

I mentioned that another benefit of using Creative Cloud for the backup is that the Database will be versioned in the cloud. This lets you go back in time if you inadvertently backup a corrupt database and need to go back a few days. To view file versions in Creative Cloud, go to your Creative Cloud account in a browser and click on Files, then click through to your Database file. Click on your Database to open the details view, and then click on the Activity link to view the file activity. Here, you can view annotations and versions in a timeline on the right. Choose the version you’d like to restore, and then either click the Restore link or the Restore icon to the left of the version.

Choose Versions from the Activity Timeline

Choose Versions from the Activity Timeline

Select a version and click Restore

Select a version and click Restore

Once you choose Restore, you will need to confirm that you really want to restore your version.

Confirm that you want to restore a version

Confirm that you want to restore a version

Once you click Restore, your previous version of the Database will be restored and will immediately begin to sync with you CC Desktop folder. Depending on your Internet speed, it may take a while for the previous version to appear on your computer. You will get an alert from CC telling you that the file has been updated. Once you get that alert, you can safely use it to replace your corrupt Outlook Database file and get back to work.

This method has saved me hours of frustration, and while I don’t wish Outlook Database corruption on you, using this method could save you hours of frustration, too.

Share on Facebook

I’ll be speaking at Adobe MAX this year!

I will be presenting a session on Variable Data Design at Adobe MAX this year. While I’ve presented at MAX previously, recently it’s been all DPS or AEM-related discussions. This talk digs deep to my roots in Data Driven Marketing and Variable Data Publishing. From the abstract:

Learn how to take personalized communications beyond email. Before email, there was data merge, which enables you to create personalized print materials using the design tools you already know and love. Whether for mailing campaigns, photo books, directories, business cards, or even t-shirts, you can use data merge to personalize your projects.

In this session, you’ll discover how to:

  • Unlock the potential of personalization in InDesign
  • Use Illustrator and Photoshop to generate personalized assets to use with InDesign
  • Manage personalization on a large scale with popular third-party variable data printing (VDP) solutions
Share on Facebook

Easy way to get notifications about the status of the DPS Services

An example of the DPS Status Dashboard

An example of the DPS Status Dashboard

Many of my customers ask how to see a dashboard that shows the status of the DPS services. You can find it at status.adobedps.com In addition to the nice dashboard like the one at the right of this text, there is also a blog that discusses upcoming maintenance and emergent issues. I encourage everyone to visit the DPS Status site from time to time just for the blog. You may be unaware of the constant innovation that happens within the DPS services, and the blog is a great place to get a glimpse into what’s happening.

Now, what if you’re wanting to know about issues before you get frustrated because something is slow or not working? Easy! Sign up for our email notification service!

Sign up for Email Notifications for when the DPS Services encounter issues

Sign up for Email Notifications

Yes, that’s right! You can get an email whenever something goes sproing! in the DPS service. If you manage a team of designers, encourage them all to subscribe so that they don’t bug you in the middle of the night with DPS service questions. It won’t help you if your designer’s close the “Interactive Overlays” panel and can’t find it anymore, but it will let them know if there’s something going on with DPS so they can let you sleep.

Share on Facebook

Restore your Twitter feed to your DPS application

Since the advent of the Twitter API V1.1, DPS customers found their embedded Twitter feeds no longer working. With the help of geniuses Josh Penrod and Emily Ragle of at Joe Zeff Design, I wrote an Adobe Developer Network article on the subject. It requires some coding and access to a publicly available web server, but it works and we’re delighted to share how to do it. (If you have my DPS Examples app installed on your iPad, and you’re reading this blog on your iPad, then tap here to see an example of a working Twitter feed in my DPS Examples app.)

Share on Facebook

Using Captivate 7 projects with DPS

I had posted a fix for using Captivate 6 HTML5 projects in DPS. In that article, I showed how to remove embedded browser check code so that your project would render without a browser check in DPS. However, in Captivate 7, removing the browser check script from the index.html file doesn’t do the job.  (If you have my DPS Examples app installed on your iPad, and you’re reading this blog on your iPad, then tap here to see examples of Captivate content running in a DPS folio.)

I asked the Captivate engineers if they had a trick up their sleeves, and this is what they delivered (thanks to Suresh Jayaraman and independently to Mayank Mahajan: if you see either of them, give them each a high five…)

  1. Open “AdobeCaptivate.ini” file present in Adobe Captivate installation folder .
  2. Add the following line of text at line 2 or line 3 of the “AdobeCaptivate.ini” file .
    • SuppressIncompatibleBrowserMessage = 1
  3. Publish the project to HTML 5

Now, the result is a folder with an index.html file. As I indicated in the earlier article, you can then make a Web Content overlay and point it at your index file. Another approach is to use the Captivate project as an HTML article rather than in a Web Content Overlay.

If you have portrait-only folio, rename the index.html file to index_v.html. If you have a landscape-only folio, rename the index.html file to index_h.html. If you have a dual-orientation folio, don’t change the name of the index.html file. In the Folio Builder panel of InDesign CC, click the “Add article” button and choose Import Article.

Add an article to your folio

Enter your article metadata and then browse to the folder that contains your Captivate project, and then click OK.

Import the HTML Article

InDesign will now seem to go into zombie mode, in which it will appear to be processing the HTML folder, but will never finish the task. The solution, which I outlined in another blog post, is to quit InDesign while it is hanging on the HTML import. Actually, what you need to do is to tell inDesign to quit, but don’t actually quit. Instead, wait, and InDesign will emerge from its coma and finish importing the HTML article.

Quit InDesign CC to complete the import

Then, you can politely tell the “Do you really want to quit?” dialog that you do not want to quit, and your HTML project from Captivate will now be safely in your folio, with no browser check. Once published, your user will need to push the “play” button on the Captivate project to start it, which is annoying to be sure. I hope the Captivate engineers will allow us one day to auto play a Captivate HTML5 project, if only in our DPS folios.

Share on Facebook