Skip navigation
1 2 3 Previous Next

FootPrints service desk

79 posts
Share This:

Hi Everyone, As discussed in the last blog, We will continue with the topic of business rule, In this topic, we will cover On-screen and On-Page load triggers.

 

Understand the processing of business rules having After Save trigger:

This topic explains how the system processes business rules having the After Save trigger.

  • The following diagram illustrates how After Save rules process when a Ticket is created manually, through email, through web services, or through another automated process.

                                                                     

 

  • The following diagram illustrates how After Save rules process when a Ticket is updated manually or updated by a rule in a previous round.

 

                                               

 

When the On Update By User Or Rule option is selected instead of the On Update By User option, if the last update was made by a user and not by a rule, the system performs around to evaluate the criteria of all such rules. After the system has gone through all the rules once, the system stops, because there would be no further updates by a user, but only by rules.

 

Example

Consider a scenario where there are 10 rules. Out of the 10 rules, five rules have the On Create option and five rules have the On Update By User Or Rule option.

When you create a new ticket, the business rules are processed. If one of the rules containing the On Update By User Or Rule option is evaluated, which results in updating a ticket, the system checks all the rules one by one again. The system stops this process only when no updates are made to a ticket.

If one of the rules using the On Create option runs and causes an update, then a new round of rules will run and all rules will be evaluated again from top to bottom. Only those using the On Update By User Or Rule option will possibly run in the 2nd or subsequent rounds.

 

Triggering sequence considerations:

 

You can have rules defined and associated with different parts of your workflows (states, transitions, groups, and entire workflows).

The order in which the system processes rules depends on the internal ordering of rules based on triggers and on administrator-defined ordering.

It is important to order your rules properly, taking into account how the rules relate to each other.

Triggers are processed in the following order.

On UpdateOn Create

1. On Exit (for State)

1. On Enter

2. On Exit (for Group)

2. On Create as part of a copy/move operation

3. On Transition

3. After Save (On Create)

4. On Enter (for Group)

 

5. On Enter (for State)

 

6. Updated in State or Group (for State)

 

7. Updated in State or Group (for Group)

 

8. Updated in any State

 

9. Updated in any Group

 

10. On any Transition

 

11. After Save (On Update By User Or Rule)

 

For linked records, the system processes rule in production as shown in the following table. In addition, Administrators should set the order for rules attached to the same part of a record definition. The best way to update the triggering order is on the Business Rules page. View the rules in the Expanded View, expanding the nodes to see the rules you want to re-order and then change the settings in the Order column.

 

OperationOn Source ItemOn Linked Item
Linked item create in state A as a result of copying
  1. Upon Item Copy
  2. On Linked Item Create
  1. On Enter (on A)
  2. On Create as part of a copy/move operation
  3. After Save (On Create)
Linked item update in state A and group G
  1. On Linked Item Update
  1. Updated in State or Group (on A)
  2. Updated in State or Group (on G)
  3. Updated in any State
  4. Updated in any Group
  5. After Save (On Update By User Or Rule)
Linked item update with transition A-B and in group G
  1. On Linked Item Update
  1. Updated in State or Group (on A)
  2. Updated in State or Group (on G)
  3. Updated in any State
  4. Updated in any Group
  5. After Save (On Update By User Or Rule)
Linked item update with transition A-B and between groups G-H
  1. On Linked Item Update
  1. On Exit (on A)
  2. On Exit (on G)
  3. On Transition (on A-B)
  4. On Enter (on H)
  5. On Enter (on B)
  6. On any Transition
  7. After Save (On Update By User Or Rule)

 

 

 

On-Screen business rule:

Select On Create, On Update, or both. This trigger is useful for assigning tickets based on category, setting field values based on other field values, giving the user informative messages based on selections they made, or changing field visibility as a user fills out a form.

Ex. Auto Assignment

 

On-Page Load

Select On Create, On Update, or both. This trigger is useful for defining default values, identifying assignees, or changing field visibility immediately when the page loads to hide fields that don't pertain to the situation or maybe revealed later while the user fills out the form. When you apply a quick template to a record, the record page refreshes and the business rule is fired based on the selected trigger.

Ex. Default Assignment

 

Best Practice for On-screen and On page load rules:

  • On-Screen business rule with On Update trigger loops and the actions are performed multiple times. Make sure that the defining criteria set on the business rule do not match after an Action has been triggered.  An action should change a value in the ticket so the rule no longer executes against that ticket.
  • Our recommendation for On-screen or On-Page load business rule is to apply of dropdown fields. If we apply On-screen rule on a simple text field with large text in it, It will give you performance issues. We should avoid applying On-screen business rule on a single line or Multiline text field if the value is not pre-populated.
  • When a field is used as Criteria in an On-Screen business rule, the rule can not apply a 'Set Field' action to that field.

 

 

We will continue to publish the next blogs on the business rule so we get more insights. So stay tuned and thanks for reading the article. Please rate the blog and add comments to share your experiences.

Share This:

Hello Everyone, In recent months, I have been publishing blogs for FootPrints, reflecting the kinds of queries we are dealing with in support. I will continue to publish those around the 20th of each month. This time we will be discussing more on the very important and most exciting topic Business rule.

 

Any time that you want the system to take action on a ticket or other item based on specific criteria, you can create a business rule. For example, you can create a rule that changes the priority of a ticket based on the subject of a request or the title of a ticket. You can also set up email reminders and set field values using formulas. You can create business rules for any type of container except address books.

 

A rule consists of three parts:

  • The trigger that defines a frequency or event causes the criteria of a rule to be checked.
  • Criteria that determine if the action should be performed (such as "Title contains 'Printer'" or "Cost is greater than 100"). Multiple criteria can be defined and are connected by AND or OR operators.
  • Actions that are performed when the criteria are met. Multiple actions can be defined and are connected by the AND operator.

 

So in the blog, we will discuss the Time-based rules and Escalation rules.

 

Defining time-based rules:

 

You can define rules that run at specific intervals and perform an action based on the results. For example, you can define a rule to run every day and check for tickets that resolved at least 14 days and status is already not equal to close.

 

 

Best Practice for Time-based rules:

  • Design time-based rules to not update a large number of tickets at the same time.
  • When you define a time-based rule, consider how the rule might affect the application data in the production instance.
  • If you have an existing time-based rule that might impact a significant number of tickets, consider defining additional business rules to achieve the same end result. If too many tickets are updated at the same time during the business hours, it might cause performance issues.
  • If possible, schedule time-based rules to run outside of business hours, especially the ones that might impact a lot of tickets. Updating too many tickets at the same time can cause performance problems for other users of the system.
  • Do not schedule multiple time-based rules to run at the same time.
  • Ensure that you configure the right schedule to run a business rule. For example, do not configure to run a business rule every 15 minutes if you can meet the business need by running it once a day.

 

Additional considerations:

  • Rules are based on the time zone of the system server.
  • Hour values are expressed in military format, that is, 1600 hours represents 4 p.m. However, 16 hours represents 16 hours from the start of the work schedule day.
  • Triggers scheduled for every other day or every other week, start fresh on the first day of the month. In production, this means that the first report of a month may occur sooner than expected based on the last report of the previous month. For example, if you run a report every other day and the last report runs on the last day of a month, the next report will run on the first day of the next month because the cycle begins fresh every month.

 

Defining Escalation rules:

 

Escalation rules can be applied in several ways: when a ticket is created or edited, after a ticket has remained open or unedited for a specified amount of time, or both. When defining escalation rules, you can base them on age or status changes or on other fields, or create special conditions (such as configuring a Generic Linking condition). For example, Once all Sub-task tickets are resolved, the Master ticket will resolve automatically.

 

 

Recurring age-based escalations are allowed. Each escalation will only run once when the ticket sufficiently ages. For example, you can create separate age-based recurring escalation rules for 5 minutes, 10 minutes, 1 hour, 2 hours, and 1 week, and each escalation rule will be applied only once to a ticket when it is sufficiently aged for that rule. You can see the (Image 1) for this example.

 

To use follow-the-sun criteria

 

For any business rule, you can specify which work schedule to use such as the Normal Work Week schedule. Rules that are assigned a schedule are not triggered outside of the work hours defined for that schedule. You may find that a rule has not run for tickets that arrive after the normal work weekends or tickets that stay in the Created state after normal work hours end.

 

To use follow-the-sun criteria, select Run any time in the Schedule Type field.

 

Configure the options for the business rule as needed to trigger the required action.

 

 

 

As the business rule is a vast concept and we need to focus on multiple areas, We will be publishing next blogs on the business rule so we get more insights. So stay tuned and thanks for reading the article. Please rate the blog and add comments to share your experiences.

Share This:

Welcome back to the first blog of the new year 2020, and this time I will be discussing the tips and tricks to improve the performance of the Footprints application. Below are the points

 

 

Influence of Time-Based Rules against a large data set:

 

Consider increasing the number of threads available for processing Time-Based Rules if the total number of Time-Based Rules that execute at the same time is large or there are many Time-Based Rules that perform complex tasks like creating new tickets. The number of threads available for processing Time-Based Rules can be configured in the Administration Console under System Management / System Settings / Miscellaneous. The default value is 10 threads and should be sufficient for typical deployments. Increasing this number does not necessarily guarantee that all Time-Based Rules will be executed faster; it depends on how many rules actually end up executing concurrently and their complexity.

 

Depending on when specific Time-Based Rules are set up to run, the number of rules whose execution schedule happens to coincide is divided amongst the number of threads specified. For example, if a deployment has 3 workspaces with a total of 40 Time-Based Rules, and at a given time 30 of those rules need to execute then 30 rules divided into 10 threads result in 3 rules executed in each thread. The number of threads that can be specified depends on an operating system, platform and available hardware resources (i.e. CPUs and memory) allocated to the FootPrints application server (i.e. Tomcat.)

 

Use caution when increasing the number of threads for it may in turn negatively impact the performance of other parts of the application if hardware resources allocated to the FootPrints application server (i.e. Tomcat) are insufficient to deal with the increased processing load.

 

Introduce an archiving process as a good practice:

 

In version 12.X/20.X, all business rules; Time-Based ones included; are executed for all existing tickets in a workspace. The automated process is only checking for each and every ticket, if it is compliant with the business rule's criteria you have set in place. If you do this against a handful of tickets, let's say a few hundred, then no problem at all, the system can cope with it.

 

If you have thousands, tens of thousands, or even hundreds of thousands of tickets in a single workspace, then you start having a performance problem and sometimes cause delays in other rules to be applied to your tickets...

 

For time-based ones, this happens every XX minutes (it is recommended not to set below 15 minutes) and takes a really long time.

We need to archive the older tickets.

 

Tickets will remain accessible, but we stop the automation on them.

 

Please find below the article for the archive process.

How to create an archiving process for Footprints 12.1.X - 20.XX ?

 

 

 

Below are some pointers which need to check-points for better performance:

 

1.) Has your SQL server been configured as per this article? The setting shown in the article is required for FP to operate optimum condition. Failing to this setting will lead to SQL deadlocks.

     https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000117068

 

2.) Did you optimize your Antivirus/Malware Tool not to interfere with Tomcat and Footprints app folders and files? If yes then we need to exclude and Tomcat and Footprints folder from      Antivirus/Malware scanning. It is not recommended though to exclude the attachment folder.

 

3.) Did you alter/customize your Tomcat server.xml? Or do you use the out-of-the-box configuration?

     How to configure Tomcat for FootPrints 12.X and 20.X onwards

 

4.) Did you optimize your java options? I assume you still use the out-of-the-box configuration?

     How to install Java for usage in FootPrints Service Core 12.X and 20.X onwards

 

5.) When was the last time the database was properly backed up and re-indexed?

     https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000112969

 

6.) I assume the instance is virtualized?  If so, is the hardware/hypervisor under strain in memory and disk IO? The FootPrints application server by default is configured to use up to 450    connections. The database server and application server must be configured accordingly; otherwise, performance will be affected. Note that by increasing the number of connections on the database server, the database host will experience increased CPU, memory and I/O activity so make sure the hosting hardware adequately supports the additional processing load.

 

7.) Are you sure that the CPU allocated to the server at least 2GHz or higher?  Consider that system requirement minimum requirement mentioned in the article, for better-performing application and database server it is crucial to understand that having more CPU is more beneficial.

       System requirements - Documentation for BMC FootPrints Service Core 12.1 - BMC Documentation

Share This:

          As a member of the Customer Support Team, We are starting a new blogging section for trending topics in each month for Footprints, And that's the reason I thought it would be good to look at what has been trending over the last couple of months since we released of supporting OpenJDK and Tomcat 8.5. I used this data to identify areas and I would like to share some tips I’ve learned from working closely with our Footprints user base.

 

Install OpenJDK and Tomcat 8.5 for an upgrade or a fresh install of Footprints 20.XX

 

The following Apache Tomcat versions are supported.

 

FootPrints VersionTomcat Version
FootPrints 20.18.03 , 20.19.XApache Tomcat Version 8.5.x (64-bit)

 

Footprints and supported JAVA versions:

 

FootPrints VersionJava Version
FootPrints 20.19.03OpenJDK 13.0.2
FootPrints 20.19.02OpenJDK 12.0.2
FootPrints 20.19.01OpenJDK 11.0.2

   

How to install OpenJDK for usage in FootPrints Service Core 20.19.X onwards:

 

 

  • Open a command window with admin rights and run the following commands to set the JAVA_HOME and PATH environment variables to point to the correct Java Version

                   setx -m JAVA_HOME "C:\Progra~1\Java\jdk-11.0.2"          

                   setx -m PATH "%PATH%;%JAVA_HOME%\bin";           

 

Note :-The SETX -m PATH command does not work correctly if the PATH has more than 1024 characters. If you have a larger path you will need to make sure that the path is correct by editing your entire path. Set JAVA_HOME environment variable and add it to the path variable too (make sure in Path variable the location is added at the beginning)

Install and Configure Tomcat 8.5 :

   

Post-installation steps to configure Tomcat by following these steps:

  • Go to the Tomcat installation folder e.g. “C:\Program Files\Apache Software Foundation\Tomcat 8.5\bin”
  • Start the Tomcat Service Wrapper (Tomcat8w.exe)
  • Select JVM from C:\Program Files\Java\jdk-11.0.2\bin\server\jvm.dll.
  • The options that you should set and the values they are set to depend on your version of Java and the application server that you use (check below table)
  • In the Initial memory pool box, enter a value of 4096.
  • In the Maximum memory pool box, enter a value not more than 80% of your maximum server memory.

 

FootPrints VersionJava OptionsJava 9 Options
FootPrints 20.19.X-Dfile.encoding=UTF-8
-XX:+UseParallelGC
-Djava.awt.headless=true
--illegal-access=permit

 

 

User-added image

 

 

For all advanced configuration settings please go through the below article.

 

https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000010914

 

 

Some issues and troubleshooting steps:

 

1. “unable to find the Catalina/localhost folder” FootPrints 2018 Release 3 requires that administrators manually upgrade Tomcat to version 8.5  If the Tomcat service is not started immediately after installation, the Catalina/localhost folder will not be created under the /conf folder. The absence of the said folder would lead to the failure of the FootPrints upgrade/install. If you have attempted the upgrade and it failed, the subsequent attempts would fail, since the installer attempts to “move” the footprints#servicedesk.xml (or footprints.xml, depending on the name you had given) file. Due to the initial failure, this file will not be available in subsequent attempts. In this scenario, please follow the steps to install Tomcat 8.5 and copy the sample footprints#servicedesk.xml file, with modifications to suit the current setup (installed location, application name, etc) File is attached below.

 

 

2. Tomcat service must be configured to use Local System service account

  1. Click Start, point to Administrative Tools, and then click Services.
  2. Right-click on Apache Tomcat service, and then click Properties.
  3. Click the Log On tab, select Local system radio button, and then click Apply.
  4. Click the General tab, and then click Start to restart the service.

 

User-added image

 

 

3. High HTTP traffic and performance issue.

 

Sometimes you may notice that there is high HTTP traffic, and you may determine that it's because the server is attempting to return high volumes of data back to the browser. In this case, if you are running Tomcat, you have the added option of turning on compression at the application server level. To enable compression adding following attribute in server.xml file in the Connector port="8080"

 

compression="on" compressionMinSize="2048"
noCompressionUserAgents="gozilla, traviata"
compressibleMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/x-javascript,
application/javascript,application/xml,application/extjson,x-font/otf,application/x-font-woff,x-font/ttf,x-font/eot"

 

 

 

 

Thanks for reading the article. Please rate the blog and add comments to share your experiences.

Share This:

FootPrints 2019 Release 2 is available for download.   Highlights of this update include:

 

  • New user interface themes that give the product a brighter and more modern look.
  • Updates to the reporting engine that improve performance in several key areas
  • Improved license management by releasing the FootPrints user license immediately upon closure of the browser
  • Improved error messaging
  • Improved LDAP address book integration
  • The merciless squishing of a number of unwanted bugs

 

For more information, please see the product release notes: https://docs.bmc.com/docs/display/FPS2019/20.19.02%3A+2019+Release+02

Share This:

I’m pleased to share with you that FootPrints 2019 Release 1 is available for download on the BMC website.

This release includes three primary changes:

 

  1. We updated FootPrints to use Open JDK as opposed to Oracle Commercial Java.   This was a major architectural change to the product that we implemented solely to prevent customers from incurring significantly increased costs due to the changes Oracle has put in place for use of Commercial Java.  By doing the work to move to Open JDK, FootPrints retains all the same functionality, with improved security, and without our customers incurring significant new fees.

 

  1. We updated the underlying reporting engine for Service Analytics. While the impact to current day to day use is minimal, it lays the foundation for performance improvements we will be delivering in upcoming releases.

 

  1. We crushed a bunch of bugs.

 

It’s important to note that moving to this release also requires changes to Tomcat, so please be sure to pay attention to the Release Notes.  As a safety backup, we’ve also put in place a process that requires a password during the upgrade.   The sole purpose of this password is to ensure customers take time to read the pre-requisites for upgrading to this release

.

If you have any questions regarding the 2019 Release 1 update, you can feel free to ask them here in the FootPrints service desk community or to reach out to our Support team for assistance.

Share This:

1. Go to the BMC communities page: : https://communities.bmc.com/community/about?view=idea

 

2. Click “Actions” on top right

 

      

3. From the drop-down list, Click “Idea”

 

     

4. Add idea details – Please be very detailed on the idea providing examples as necessary.

     

5. Click on “Publish” on bottom of page

 

For more information, please refer to Ideas FAQ's

Share This:

Problem:

FootPrints 2018 Release 3 requires that administrators manually upgrade Tomcat to version 8.5  If the Tomcat service is not started immediately after installation, the Catalina/localhost folder will not be created under the /conf folder. The absence of the said folder would lead to the failure of the FootPrints upgrade/install.

 

Resolution:

The issue “unable to find the Catalina/localhost folder” in Tomcat 8.5 will be addressed in 20.19.01. If user(s) want to upgrade prior to the 20.19.01, then check for the type of install and proceed with appropriate steps.

 

The steps for the resolution would be based on if the user(s) have attempted the 20.18.03 install or yet to install.

 

If Tomcat 8.5 has not yet been installed

  1. Install Tomcat 8.5 and follow the instructions for the same
  2. At the end of the setup, user(s) can perform the following
    1. Do select the “Run Apache Tomcat” option
    2. If the above option was not selected for configuration changes, continue with next steps
  3. Make necessary configuration changes for Java, memory, etc. and start it once to ensure that the values are indeed correct
  4. User(s) can stop the Tomcat server prior to the FP installation

 

This action would ensure that the /Catalina/localhost folder is created and the installer would function just like any other update.

 

Attempted install and encountered error

There could be chances that user(s) may have attempted to install and encountered error during the process. This can be corrected based on the install type:

 

New Installation

If you have attempted the new install and encountered the error, simplest way is to clean up the server for any partially installed application files, database, etc., follow the steps mentioned for the Tomcat 8.5 installation above and start the FootPrints installation again.

 

Upgrade installation

If users have attempted the upgrade and it failed, the subsequent attempts would fail, since the installer attempts to “move” the footprints#servicedesk.xml (or footprints.xml, depending on the name you had given) file. Due to the initial failure, this file will not be available in subsequent attempts. In this scenario, please follow the steps to install Tomcat 8.5 and copy the sample footprints#servicedesk.xml file, with modifications to suit the current setup (installed location, application name, etc)

 

Note: Since the current action of the installer is to “move” the existing “footprints#servicedesk.xml” file, it’s good to take a backup of the same prior to start the FootPrints 2018 Release 3 upgrade.

 

If you still face issues during the install, do contact BMC support for further assistance.

Share This:

Hi Everyone,

 

If you haven’t been to the download site recently, it’s worth heading there now.  We’ve released two new versions of the product since our last blog post and there are some worthwhile updates for you.   In these releases, we’ve put a lot of work into making Footprints more secure, reliable, and performant than ever.   We’ve also put in a number of functionality enhancements for you as well.   Some of these improvements include:

  • Create a single search for records assigned to teams
  • Search for records that need approvals
  • Support for CentOS Linux 6 & 7
  • Ability to copy email templates
  • Ability to configure complex passwords
  • And many other updates.

We’ve also crushed a lot of bugs while making these updates.

 

To see all the changes and bug squashings, please check out the release notes for both releases: 

 

  As you can see from above, we’ve also changed the model we use for version numbering.   Moving forward will now use a model that calls out the year and the release number of each update.   Since our most recent release was the second release during 2018, it’s now called FootPrints 2018 Release 2.   Our next release in 2018 will be called FootPrints 2018 Release 3.   When we release in 2019, the first release will be called FootPrints 2019 Release 1.   If you have any questions about the new numbering model, feel free to post it in the comments below and I’ll be happy to reply.

 

I hope you enjoy the changes to the product.  Thank you for your business, and Happy FootPrintsing!

 

 

Share This:

I'd like to formally announce the release of FootPrints 12.1.08 with the recent release of patch 12.1.08.001.

 

As we continue on with our quarterly release cycle, I am pleased to see this release deliver some key user experience enhancements.  This will benefit both administrators as well as day to day users like agents and customers.  Agents and customers will now be able to copy images from the clipboard into a ticket which will save them significant time when trying to visual communicate a problem or solution.  Agents and administrators will both benefit from seeing the name of the rule that made a change to their tickets when viewing the ticket history.  This will help both with troubleshooting as well as understanding the flow of the business rules.  Those tasked with having to create multiple, similar searches will save significant time by making use of the ability to copy existing searches.  Copy is also now available for Quick Templates to save administrators time as well.  These last 2 are part of the most highly requested Idea on the public community regarding copy.  See the full release notes here.  The quickest way to get to the download is by clicking here.

 

Happy FootPrintsing!

Share This:

I'd like to officially announce the release of FootPrints 11.6.10 with our recent release of 11.6.10.001.  It has been almost 2 years since the release of 11.6.09 so and a lot has been done in that time.  Since we are in maintenance mode with the version 11 platform the main focus was making sure our 3rd party platform support was up to date which also helped with our goal to protect our customers by limiting newer security threats.  We were also able to fix some high priority defects as well some customers have been experiencing.  I have highlighted the major changes for 11.6.10 below.   Full details of what is included in this release can be found in the release notes here.  The quickest link to get the download is here.  Happy FootPrintsing!

 

What’s New

FootPrints 11.6.10 is the tenth service pack for the 11.6 version primarily focused on defect corrections. Before you upgrade, note the following key changes in version 11.6.10:

  • Updated version of Perl and related libraries: This release uses and includes the BMC compiled Perl version 5.24.1 coming from ActiveState Perl 5.10.0 in previous versions. This provides the security enhancements that are a part of a newer version of Perl.
  • Updated version of server side JAVA and Tomcat for Windows installs: This release includes an upgraded Java version 8u112 and Tomcat version 8.5.8 for better security and stability for the Executive Dashboard and all reporting charts and graphs.
  • Search and Report configuration now stored in the database: Previously all search and report configuration were stored in text files and the upgrade moved all that information to database tables. This release provides an enhanced stability, better management, and better performance for searching and reporting.
  • Windows 2016 support: This release provides an official support for the Windows 2016 platform for the FootPrints server.
  • Various performance and security improvements
Share This:

The conference is only a week and a half away.

 

Join us at the T3 Service Management and Automation Conference November 6-10 in Las Vegas to learn about these things and many other great topics.

 

Here is a list of the FootPrints sessions that you might be interested in: 

 

Session

Speakers

FootPrints: Creative Business Process Solutions

Rocky Fly, O'Reilly Auto Parts

FootPrints: Getting Started with Version 12

Greg Gielda, Flycast Partners

How to Get the Most out of FootPrints V12 Service Analytics

Kam Akrami, Rightstar

FootPrints SLA: The Art of the Deal

Kam Akrami, Rightstar

FootPrints Configuration Management: A Fool with a Tool is Still a Fool

Greg Gielda, Flycast Partners

What's Coming on the BMC Client Management and FootPrints Roadmap?

Don Cholish, BMC

What's Coming on the BMC Client Management and
FootPrints Roadmaps?

Serena Lambiase and Don Cholish, BMC

 

Also, since many FootPrints customers also own BCM, we made sure there was no overlap of session times.  Make sure to also check out these BCM sessions.

 

Session

Speakers

What's New in BMC Client Management 12.6?

Serena Lambiase, BMC

Getting More our of your BMC Client Management

Steve Gibbs , Rightstar

Integrations that Add Value to your BMC Client Management Investment

Kyle Hamilton , Flycast Partners

Simplify, Elevate and Automate with RemedyForce
Agent Discovery and Client Management

John Fulton , BMC

How BMC Client Management can Protect You From

Aaron Sebastian, BMC

How BMC Client Management can Help One to Prepare for an Audit

Kyle Hamilton, Flycast Partners

Client Management Focus Group

Serena Lambiase, BMC

 

You can check out other topics here:

http://www.tooltechtrain.com/downloads/T3SMAC_Schedules.pdf

 

We hope to see you there!

Share This:

We'd like to announce that the latest version of FootPrints, 12.1.05, is now fully available for download.  Please feel free to review the release notes by clicking here.  In addition to defect correction, this release addresses Ideas submitted by Alessandro Ghezzi and Paul Tipping. You can download by clicking here.  This is our 3rd consecutive release sticking to our quarterly release cycle so expect more of the same for the remainder of 2017.

Share This:

I have some good news.  There has been an issue going on for a while now where the Ideas automation system was misbehaving and setting some Ideas to "Not Planned" prematurely.  I finally got this corrected this week.   As a result, you will likely see all Ideas created since July set as New as they weren't recognized by the automation tool previously.

 

I'd also like to announce some changes to the thresholds themselves.  Previously Ideas that were at least 180 days old and in the bottom 50% were automatically set to "Not Planned"  I have significantly reduced this to the bottom 10%.   I think we can all agree if an Idea can't climb out of the bottom 10% after 6 months, it is not a high priority.  I think this will reduce the number of times people feel an Idea is archived too soon.

 

Lastly, all delivered Ideas will now always remain view able so we are not hiding our accomplishments.

 

I hope these changes make for a better Ideas automation experience.

Share This:

We'd like to announce that the latest version of FootPrints, 12.1.04.001, is now fully available for download.  Please feel free to review the release notes by clicking here.   This release introduces some user experience improvements that should help your agents productivity.  This release addresses Ideas submitted by Bernadeth Raquiza, Jean AD, Paul Tipping, and Cristy Castano.  Thanks for all the great feedback.  Look forward to a more rapid release cycle in 2017 that focusing on delivering value quickly to everyone.

Filter Blog

By date:
By tag: