Checking In Files from Surround SCM Web

You may not have access to use the Surround SCM desktop client in some cases, such as when you are working from home, at a customer site, or in a QA lab. In this case, you may be able to use Surround SCM Web to work with files.

Surround SCM Web 2016.1 introduces the ability to check in files, which helps you share changes with other users when you cannot access the desktop client.

How to check in a file

To check in a file from Surround SCM Web:

  1. Click the filename in the Contents tab on the Source tab.
  2. Click checkinfilebutton on the View tab.
    checkinbutton
  3. In the Check In File dialog box, click browseforlocationbutton. Browse to select the File to check in and click Open. The filename is added to the File to check in field. checkinfile
  4. Select the file Version to change. Make sure you select the correct version.
  5. Enter any Comments.
  6. Select Skip server auto-merge to check in the file without merging changes. The checked in file becomes the new version even if another user changed and checked in the file before you.
  7. Select Update version even if no change is made to increment the version number even if you did not make changes.
    You may want to select this option if you are working with related files and always want the version numbers to match. This can help you and your team visually confirm that files are in sync and changes were not missed. For example, you work with two related files: WysiWrite.cpp and WysiWrite.h. Both are currently version 29. You make changes to WysiWrite.cpp. WysiWrite.h does not have changes. If you select this option at check in, both files are updated to version 30. If you do not select this option, WysiWrite.h remains at version 29.
  8. Click Check In to check in the file.

Limitations

If you already use the Surround SCM desktop client, note some limitations and differences to consider when checking in files from Surround SCM Web.

  • You can only check in one file at a time.
  • You cannot check out files and working directories are not used.
  • You cannot check in files if your team requires using changelists, adding files to code reviews, or attaching files to TestTrack at check in. Use the desktop client to check in files in these scenarios.
  • File dialog default user options for check ins set in the desktop client are ignored.

Version management

A handy tip about managing the file versions when using Surround SCM for check ins:

When you get a file from Surround SCM that you plan to change, note the version number so you can select that version at check in. When checking in from Surround SCM Web, you must manually select the file version you retrieved and changed. Surround SCM needs to know the version you started with so it can correctly merge your changes with other users’ checked in changes. In the desktop client, you do not need to select a version at check in because version information is automatically tracked in the .MySCMServerInfo file in your working directory, which is not used by Surround SCM Web.

More information

See the Surround SCM Web help for more information about checking in files.


What’s New in Surround SCM 2016.1 Documentation

If you haven’t upgraded to Surround SCM 2016.1 yet, definitely consider doing it soon. This release has some nice new features and enhancements that you’ll want to take advantage of.

Here are some documentation updates to look at to get familiar with what’s new.

Continue reading “What’s New in Surround SCM 2016.1 Documentation”


Webinar: What’s New in Surround SCM 2016.1

webinarSurround SCM isn’t your average version control solution—it includes unique features that set it apart from competitive products, such as workflow automation, electronic signatures, and built-in code reviews. And new Surround SCM 2016.1 is big on often-requested features like:

Continue reading “Webinar: What’s New in Surround SCM 2016.1”


Just Released! Surround SCM 2016.1

Surround SCM 2016.1 is now available. In addition to tighter TestTrack integration, improved label management, and JIRA 7 integration, this release also includes web client enhancements.

If you’re working off site and need to make a quick change to a file, or working in the QA lab and missing the files files, you can now use the Surround SCM Web client to check in a changed file or quickly download all the files in a repository.

Check In Files from the Surround SCM Web Client

Learn more and see what’s new in Surround SCM 2016.1.


Storing Microsoft Word Documents in Surround SCM

While an SCM tool is often associated with source code, Surround SCM can be used across the enterprise to keep track of various Microsoft Word documents such as legal contracts or process documentation. Storing these types of documents in an SCM tool makes it easy to identify the latest version of the document and to answer the questions of who/what/when/why associated with each change. If you are looking to version control your Microsoft Word documents, check out the following Surround SCM features that will make your life easier.

Document differences

The History window shows a list of all the file’s historic versions. Select two file versions and then use the Differences command to view the changes made between the two file versions. Users can customize the differencing tool associated with a file extension via Surround SCM’s user options. By default in Surround SCM, the .doc and .docx file extensions are associated with the Microsoft Word Compare tool, so Surround SCM can seamlessly integrate with Word.

Find In Files

When searching file contents for a particular text, most SCM tools limit the search/grep capabilities only to text files. In addition to searching text files, Surround SCM also provides functionality for searching various binary file formats including Microsoft Word (.doc, .docx), Microsoft Excel (.xls, .xlsx), Adobe PDF (.pdf), Open Document Format (.odf), and Rich Text Format (.rtf). In order to search binary files, turn on branch indexing, which also speeds up search operations.

Shadow folders

If some people who read the process documents are not SCM users, consider configuring a shadow folder in Surround SCM. A shadow folder contains a copy of the most recent version of files. By configuring a network directory as a shadow folder for your SCM folder, every time the document is modified Surround SCM will automatically store a copy of the latest version in this network directory. Other people can access this network folder at any point in time to see the most recent document changes without even needing the Surround SCM application. Configure a web server directory as a shadow folder and the document changes are automatically published to your website.

Email Notifications

When a process document changes, many companies require the document author to notify all relevant parties about the process change, but that depends on a person remembering to take action. Take away this human dependency by configuring Surround SCM to send an email to people every time the document is changed. The email message can include information such as who made the change and why the change was made. If a shadow folder is configured, the email could also contain a link to the shadow folder network location. Not only does automated emails ensure your notification process is consistently followed, auditors love this type of automation.

Electronic Signatures

Regulated or audited industries may require that process changes be signed off by a specific person for legal/contractual reasons. Surround SCM provides electronic signature functionality to fulfill this obligation. The electronic signatures are stored in the audit trail so auditors can inspect that the proper process was followed.

Microsoft Office integration

Surround SCM supports integration with Microsoft Word, Excel, PowerPoint, and Project. This Microsoft Office integration gives you access to the following commands from the Surround SCM menu in Office applications: Add, Get, Check Out, Undo Check Out, Check In, History, and Properties.


New and Improved TestTrack and Surround SCM Security Best Practices

Best practicesWhether you’re just getting started with TestTrack or Surround SCM or you’ve been using them for years, it’s always a good idea to regularly evaluate the security measures you have in place and make sure you’re taking the proper steps to keep your data secure. With the help of Seapine security experts, we’ve recently updated the TestTrack and Surround SCM Security Best Practices with additional and more current information that can help you properly manage your Seapine product servers and avoid common mistakes that could leave your data vulnerable to theft, damage, or loss.

If you agree that keeping your data secure is of critical importance, you should definitely check them out:

TestTrack Security Best Practices | Surround SCM Security Best Practices


Let's Go!

Jump into Seapine today.

© 2017 Seapine Software. All Rights Reserved.

Privacy Policy | Site Map