Processing Ajax...

Title

Message

Confirm

Confirm

Confirm

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure?

Top WallpaperFusion Members for February 2019

March 1, 2019
Congratulations to our top contributing members for February 2019! They have been hard at work submitting, rating, and discussing images on WallpaperFusion, and have racked up some impressive reputation scores along the way!
Contributors
1.
Alan Wade's profile on WallpaperFusion.com
2.
izann's profile on WallpaperFusion.com
3.
Laodurias' profile on WallpaperFusion.com
4.
Tony Kohlruss' profile on WallpaperFusion.com
5.
DLJunkie's profile on WallpaperFusion.com
6.
Judith Lane's profile on WallpaperFusion.com
7.
Kirk Meyer's profile on WallpaperFusion.com
8.
Nicolas Deleglise's profile on WallpaperFusion.com
9.
Daniel Parker's profile on WallpaperFusion.com
10.
michael oakes5's profile on WallpaperFusion.com
JigsawMania
1.
Laodurias' profile on WallpaperFusion.com
2.
sandy17's profile on WallpaperFusion.com
3.
cherbear48's profile on WallpaperFusion.com
4.
masa2's profile on WallpaperFusion.com
5.
Tsula's profile on WallpaperFusion.com
6.
Pamala McGlothlin's profile on WallpaperFusion.com
7.
aba3's profile on WallpaperFusion.com
8.
Moanerz77's profile on WallpaperFusion.com
9.
Sly's profile on WallpaperFusion.com
10.
BGL's profile on WallpaperFusion.com
Check out the current top members or look at previous months on our Top Members page!

Introducing Widgets!

February 25, 2019

We're very excited to announce a powerful new feature, Widgets! CloudShow Widgets allow you to overlay extra information on your content frames. You can add clocks, weather information, custom text/HTML, background audio/music, and more. To get started with Widgets just click the App icon for your content frame to open the radial menu.

Widgets
Widgets

Once the radial menu is open, click the Widgets icon and you'll be presented with a list of all the currently available widgets. Select the Widget you would like to add, then adjust it's settings and position.

Widgets
Widgets

Voila, you're all set! In the preview below you can see a clock overlaid on the News app. You can customize the look, location, size and more for each widget.

Content Frame with Clock Widget
Content Frame with Clock Widget

Try out the new Widgets feature today!

CheckCentral API Documentation: createCheck Endpoint

February 21, 2019

The CheckCentral API provides an endpoint for creating checks programmatically. All of the configuration options are available through the API, detailed below. To create a new check through the API, you will require an API token for your organization with Read/Write access. Organization administrators can create tokens through the API portal on your dashboard.

The endpoint is located at https://api.checkcentral.cc/createCheck/?apiToken=APITOKEN where the APITOKEN placeholder is replaced with your valid token. The request must be made with the Content-Type header set to application/json. The body of the request should contain as many of the properties listed below as required to define the check. Any properties not passed will be set to their default value.

For example, to create a new check that:

  • Receives messages at the address "demo+apicheck@mycheckcentral.cc"
  • Expects messages every two hours
  • Expects messages only on weekdays
  • Is set to Failure unless the message subject is "Message Success" or the message body has the text "No Errors Reported"

you would send the following json in the body of the request:

Code

{
  "name": "An API Check",
  "email_alias": "apicheck",
  "interval_type": "hour",
  "interval_value": 2,
  "active_days": [
    "mon",
    "tue",
    "wed",
    "thu",
    "fri"
  ],
  "success_conditions": {
    "required_conditions": "any",
    "conditions": [
      {
        "message_field": "subject",
        "matches": "exactly",
        "value": "Message Success"
      },
      {
        "message_field": "body",
        "matches": "contains",
        "value": "No Errors Reported"
      }
    ]
  }
}

The check data must include a name property, as well as at least one of email_alias and matching_conditions to allow the check to be matched against incoming messages.

The complete list of possible properties for check configuration are as follows:

Check Structure

Parameter Type/Allowed Values Default

name

The name for the new check.

The name parameter is required.

String

email_alias

The plus alias for the check. This will be used to generate the custom email address for the Check along with your organization account name: account_name+email_alias@mycheckcentral.cc.

At least one of the email_alias or matching_conditions parameters must be specified.

String

matching_conditions

The rules that will be used to match incoming messages. See the definition of a ConditionGroup below.

At least one of the email_alias or matching_conditions parameters must be specified.

ConditionGroup {}

group_id

The ID of the group to assign this check. IDs may be retrieved from the getGroups API endpoint.

String

description

A text description for the check.

String

interval_type

The interval unit CheckCentral will use to calculate the expected arrival time of incoming messages

One of:

  • minute
  • hour
  • day
  • week
  • month
day

interval_value

The number of interval units (see above) used when calculating the expected arrival of incoming messages.

Integer 1

overdue_minutes

How many minutes after the interval has elapsed CheckCentral will wait before flagging the check as failed.

Integer 30

window_start

An optional time of day when messages will begin to be received.

String 00:00

window_end

An optional time of day when messages will cease to be received.

String 00:00

active_days

Pass an array of days to indicate which days the check should expect to receive messages.

An array containing either "all", or any of:

  • sun
  • mon
  • tue
  • wed
  • thu
  • fri
  • sat
[ "all" ]

enabled_notifications

Pass an array of personal notification services to configure the check to send alerts via those services.

An array containing any of:

  • email
  • sms
  • push
  • pushbullet
  • pushover
[]

enabled_notification_channels

Pass an array of organization notification channel IDs to configure the check to send alerts via those services. IDs may be retrieved from the getNotificationChannels API endpoint.

Array[String]

[]

enabled_ticketing_systems

Pass an array of organization external ticketing system IDs to configure the check to create and update tickets via those services. IDs may be retrieved from the getTicketingSystems API endpoint.

Array[String]

[]

notify_returned_to_success

Checks with this flag will send an alert when they are restored to a success state by an incoming message.

Bool true

notify_outside_window

Checks with this flag set to false will only send alerts during the time window and active days configured above.

Bool true

notify_consecutive_alerts

This parameter controls when CheckCentral will send alerts about repeated failure or warning messages.

One of:

  • always
  • first
  • after_n
  • every_nth
always

notify_consecutive_alerts_limit

If notify_consecutive_alerts is set to either after_n or every_nth, this parameter configures how many consecutive failures or consecutive warnings will trigger alerts.

Integer 1

notify_failure_grace_period

The number of minutes this check will wait to send alerts about failures. If the check is returned to successful status before this period elapses, any pending alerts will be cancelled.

Integer 0

default_status

The default status for incoming messages that don't match against any of the conditions below.

One of:

  • success
  • warning
  • failure
failure

success_conditions

The rules that determine whether incoming messages will be set to success. See the definition of a ConditionGroup below.

ConditionGroup {}

warning_conditions

The rules that determine whether incoming messages will be set to warning. See the definition of a ConditionGroup below.

ConditionGroup {}

failure_conditions

The rules that determine whether incoming messages will be set to failure. See the definition of a ConditionGroup below.

ConditionGroup {}

ConditionGroup

Parameter Type/Allowed Values Default

required_conditions

This parameter controls whether incoming messages must meet any or all of the conditions defined below to be considered a match.

One of:

  • all
  • any
"all"

condense_whitespace

If this flag is set, all of the conditions defined in this group will treat multiple whitespace characters as a single space.

Bool false

conditions

The list of conditions for this ConditionGroup to match messages against. See the definition of a Condition below.

Array[Condition] []

Condition

Parameter Type/Allowed Values Default

message_field

Which part of the incoming message will be examined for this condition.

One of:

  • subject
  • body
  • to
  • cc
  • attachments
  • attachment_text
  • from
  • originally_to
subject

matches

What matching rule this condition will use.

One of:

  • contains
  • not_contains
  • exactly
  • empty
  • not_empty
  • has_attachments
  • has_no_attachments
  • filename_contains
  • filename_not_contains
  • filename_exact
  • text_contains
  • text_not_contains
  • complex_match
  • complex_filename_match
  • complex_text_match
contains

value

The value to use with the above matching rule and message component.

String

ClipboardFusion 5.5 Now Available!

February 21, 2019

We're very excited to announce that ClipboardFusion 5.5 is now available for download! We've fixed a few bugs, improved the way our servers talk to ClipboardFusion, and added a new Macro function for a listview box with filtering capabilities!

ClipboardFusion 5.5 Highlights

  • Change: Push syncing improvements
  • Change: New Macro function to open a listview window with filter (BFS.Dialog.GetUserInputListViewWithFilter)
  • Fix: UI no longer hangs during a sync
  • Fix: Settings restore now restores and binds the hotkeys correctly
  • Fix: General fixes and improvements

Updating ClipboardFusion

We encourage everyone to update to the new version today to take advantage of these improvements. If you would like to see a complete list of all the changes, please view the ClipboardFusion Change Log. We would also like to thank all of the translators who have helped translate ClipboardFusion to their native languages.

ClipboardFusion Screenshots

Clipboard Manager > History List
Clipboard Manager > History List

Upload Content from Dropbox, Google Drive, and Microsoft OneDrive!

February 14, 2019

CloudShow now supports uploading content from 3 new online sources: Dropbox, Google Drive, and Microsoft OneDrive! Using the all-new upload source selector you can choose where you upload your content from.

Upload Selector
Upload Selector

Your Computer

As before you can still upload content from your computer, and CloudShow now supports multiple file uploads at once. Just ctrl+click multiple files to select more than one and upload them at the same time.

Upload from Your Computer
Upload from Your Computer

Dropbox

If you store your files in Dropbox for work or personal use, CloudShow can access them now. You just need to authorize CloudShow to connect to your Dropbox account (as read-only) then just browse to the files you need.

Upload from Dropbox
Upload from Dropbox

Google Drive

If you use Google Drive to store your media files, CloudShow can now download them into your content section. Once you authorize CloudShow to connect to your Google Drive account (as read-only) your files are just a few clicks away.

Upload from Google Drive
Upload from Google Drive

Microsoft OneDrive

If you're a Microsoft OneDrive user, you're in luck! CloudShow can now pull content from your OneDrive account into your CloudShow content. Simply authorize CloudShow to access your OneDrive files (as read-only) and you're all set.

Upload from Microsoft OneDrive
Upload from Microsoft OneDrive

Start Uploading Today!

Uploading files to your CloudShow content area is now easier than ever. Check out the new upload providers today!

Checking Website Certificate Expiry Dates with CheckCentral

February 4, 2019
We've recently released a Direct Integration built for checking SSL/TLS certificate expiry dates. The script for this guide will still work, but we would highly recommend using the built-in integration for it. You can get started with the Direct Integration by navigating to your CheckCentral dashboard and clicking Services > Direct Integrations in the top menu.
If you have websites for which you maintain the SSL certificates, this PowerShell script will help more efficiently monitor the expiration status of those certificates. The script can be run from anywhere, as it connects to the public URL for the website, and it will email the results wherever you like. This help guide shows how to configure the script to email the results to CheckCentral and create a companion Check to automate the status parsing.
Checks can be added from various locations in the CheckCentral interface, from the Dashboard, Checks page, Activity page, and the Check Group details page.
  • Begin by clicking "
    Add Check
    ."
Add Check
  • Select "Start Fresh," and click "Start."
Create Check
  • Name the Check. It can be whatever you like, for example
    Website Certificate Expiry Check
    .
  • Select an existing Check Group or create a new one by clicking group_icon.png
    Add Check Group
    .
  • Select an existing Label or create a new one by typing the name in the text field of the dropdown. (optional)
  • Add a description (optional).
  • The Asset ID is used exclusively with certain ticketing systems and is not required for Checks. Asset ID details and ticketing systems are more fully covered by other documents (e.g. Halo Integration (asset ID).)
  • Leave the Asset ID blank.
Your Check so far will look something like this:
Step 1: Identification
Navigate to the next step in CheckCentral by clicking the "Next" button or the tab name.
  • Leave "Scheduled" selected as we will be running the script regularly.
  • Assuming you'll run the script daily, leave the Expected Interval on "1" "Day(s)." If you plan to run the script on another interval, adjust accordingly.
  • The initial expectation time is set by the first email message that is received and processed by its Check. (For example, if a notification email arrives at noon and its Check is set for every half hour, it will expect another notification email at 12:30.)
  • Leave the Set as Overdue setting at "After 30 Minutes." If the script notification email is not received after this amount of time has been exceeded, the Check will be marked as a failure.
Leave Custom Schedule de-selected.
Step 2: Schedule
The Matching step is what matches a notification email to its specific Check. It's also where you'll set the notification's CheckCentral destination email. For CheckCentral to parse notification emails, they must be sent to a "mycheckcentral.cc" address. By default, the email address is [your organization name]@mycheckcentral.cc.
A more unique email address is created using the name given to the Check (with white spaces removed).
  • Leave the default selections enabled.
  • Copy the unique email address for later use by clicking on the Copy icon copy.png.
Do not add any matching rules. The unique email address is sufficient.
Step 3: Matching
The email address will appear different based on your organization name and the name you specified for your check.
The previous Matching step identifies the incoming email to the Check. The Status step looks for indicators of what type of notification you're receiving (e.g. The job was successfully run, it failed, or there were some issues.) The configuration options you choose can vary considerably, but the approach is the same.
The Default Status is what is set when the other Rules in this step don't match. Criteria for the remaining statuses then need to be defined, requiring their own unique one-to-one matches.
  • Leave the Default Status on "Failure."
  • The "Success Criteria" section is where you'll set the criteria that will mark an activity as successful.
  • Click
    Add Success Rule
    .
  • A successful run (no certificates expired or expiring soon) of the script will have the word "SUCCESS" in the email Subject.
  • Set the rule to "Subject contains SUCCESS" by leaving the default dropdown selections and typing
    SUCCESS
    (all caps) in the empty text field.
  • The "Warning Criteria" section is where you'll set the criteria that will mark an activity with a warning.
  • Click
    Add Warning Rule
    .
Step 4: Status
A warning result (certificate(s) expiring soon) from the script will have the word "WARN" in the email Subject.
  • Set the rule to "Subject contains WARN" by leaving the default dropdown selections and typing
    WARN
    (all caps) in the empty text field.
Leave the Condense Whitespace and Combine Attachments checkboxes enabled.
Notification Fields
Notifications are simply how you want to be informed of Check Failures, Warnings, and some other Status changes.
Email, push, chat and other software can be integrated as well as ticketing systems, allowing for automatic ticket creation and management.
Further configuration is required for each to function and is done via the Notifications tab in the main menu. They can be configured before or after Check creation.
For more understanding of Notification setup, see the CheckCentral Beginner's Guide (Notifications).
  • Select the desired means of Notification. If in doubt of the selections here, leave the defaults.
  • From the Save tab, click the "Save Check" button.
With the Check configured in CheckCentral, you need to install the script onto a machine (where it will regularly run).
  • Download the script: CheckWebsiteCertExpiry.zip.
  • Extract it somewhere on the computer (e.g. C:\Scripts). There will be three files: CheckWebsiteCertificateExpiry.ps1, createScheduledTask.ps1, and websites.txt
  • Edit the websites.txt file to contain the list of websites you want the script to check. Save it. Make sure to put one URL on each line.
  • Open a PowerShell console and run the script to make sure it works. For example:

    Code

    .\CheckWebsiteCertExpiry.ps1 -Websites (Get-Content websites.txt) -EmailFromAddress {Email From Address} -EmailToAddress {Check Email Address}
  • Refresh the Check page or Dashboard to see the new Activity for your Check.
  • You're ready to set up the Windows Scheduled Task so the script will automatically run each day.
  • First, edit the parameters at the top of the CreateScheduledTask.ps1 script and save the changes.
  • You'll see the new Scheduled Task in the Windows Task Scheduler. Run it and verify that a second Activity shows up in the CheckCentral Check.
Test
For more detail on Check creation and best practices, see our Check Creation Guide.
For other guides and support contact information, see CheckCentral Support
First Page
Previous Page
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
Next Page
Last Page