- 基本情報
- セットアップと構成
- オートメーション プロジェクト
- 依存関係
- ワークフローの種類
- 制御フロー
- ファイルの比較
- オートメーションのベスト プラクティス
- ソース管理との連携
- デバッグ
- ログ
- 診断ツール
- ワークフロー アナライザー
- ワークフロー アナライザーについて
- ST-DBP-002 - 多数の引数
- ST-DBP-003 - 空の catch ブロック
- ST-DBP-007 - 複数のフローチャートレイヤー
- ST-DPB-010 - [ワークフロー] または [テスト ケース] の複数のインスタンス
- ST-DBP-020 - 未定義の出力プロパティ
- ST-DBP-021 - ハードコードされたタイムアウト
- ST-DBP-023 - 空のワークフロー
- ST-DBP-024 - 永続性アクティビティの確認
- ST-DBP-025 - 変数のシリアル化の前提条件
- ST-DBP-027 - Persistence のベスト プラクティス
- ST-DBP-028 - 引数のシリアル化の前提条件
- ST-USG-005 - ハードコードされたアクティビティのプロパティ
- ST-USG-009 - 未使用の変数
- ST-USG-010 - 未使用の依存関係
- ST-USG-014 - パッケージの制限
- ST-USG-017 - パラメーターの修飾子が無効
- ST-USG-020 - 最小ログ メッセージ
- ST-USG-024 - 未使用で保存されたままの値
- ST-USG-025 - 保存した値の誤用
- ST-USG-026 - アクティビティの制限
- ST-USG-027 - 必要なパッケージ
- ST-USG-028 - ファイル テンプレートの呼び出しの制限
- ST-USG-027 - 必須のタグ
- ST-USG-034 - Automation Hub URL
- 変数
- 引数
- インポートされた名前空間
- コード化されたオートメーション
- トリガーベースの有人オートメーション
- オブジェクト リポジトリ
- ScreenScrapeJavaSupport ツール
- 拡張機能
- Studio でのテスト
- トラブルシューティング
GSuite activities not supported by the Activity Migrator tool when migrating Studio automation projects.
サポートされていないアクティビティ
Refer to the tables below for the GSuite activities that are unsupported when using the Activity Migrator tool. These classic activities have no modern counterpart. The migrator emits an action-required Static Analysis Results Interchange Format (SARIF) entry and leaves the activity in the workflow.
| サービス | Classic Activity |
|---|---|
| Apps Script | Create Deployment (CreateScriptDeployment) Create Script Project ( CreateScriptProject) Get Project Content ( GetProjectContent) Upload Script File ( UploadScriptFile) |
| ドキュメント | Get Text Index (GetTextIndex) Batch Document Updates ( BatchUpdateDocumentScope) |
| シート | Copy Sheet (CopySheet) Batch Spreadsheet Updates ( BatchUpdateValuesScope) Download Spreadsheet ( DownloadSpreadsheet) Get Sheets ( GetSheets) |
Unsupported / partially-supported properties
Properties that are dropped (no modern equivalent at all) or that can only be migrated conditionally, by activity. Any property not listed here is migrated normally. Anything that cannot be migrated produces either a warning or an action-required entry in the SARIF report (and a corresponding annotation on the migrated activity in the .xaml).
横断的
ContinueOnErroron every modern target — the modern Connection-Service activities don't exposeContinueOnError. The migrator logs an action required so the user can re-implement the equivalent with a TryCatch if needed.
予定表/カレンダー
ModifyEvent.InstancesOption— onlyTHIS_EVENT(or null) is supported; any other value emits an action required and the property is dropped.
シート
AddNewSheet.Rows/AddNewSheet.Columns— no modern equivalent; emits an action required when bound.CreateNewSpreadsheet.Rows/CreateNewSpreadsheet.Columns— same as above.AddDeleteColumns.Name(INSERT mode) — column-letter form cannot be auto-converted to the modernColumnPosition(int); emits an action required so the user can set it manually.WriteRange.Result— the modern activity has no equivalent string output; emits an action required so the user can remove downstream usage.
ドライブ
CreateFilePermission.EmailMessage—ShareFileFolderConnectionshardcodes its email body tostring.Emptyand exposes no input; the migrator drops the value with an unsupported warning.CreateFilePermission.Result— modern activity exposes onlyAccessUrl(string) instead of a structuredPermissionobject; emits an action required.FindFilessearch location — the modern activity requires a location and does not support "search everywhere", so the migrator hardcodesItem.IdOrUrl = "root"(My Drive) and emits an action required telling the user to override it if needed.
User actions the migrator generates
Every action-required entry shows up both in the SARIF report and as an annotation on the migrated activity in the produced .xaml. Ordered by frequency:
| Action-required entry | 説明 |
|---|---|
ContinueOnError is unsupported. | Emitted on virtually every migrated activity. Suggests the user wrap the activity in a TryCatch if they need the same semantics. |
Result output type changed (auto-bridged via HTTP Request). | Emitted by FindFiles, GetFileInfo, GetFilePermissions, UpdateFilePermission, GetCellColor, GetDocument, SearchEvents whenever the bridge fires. Tells the user to verify the generated HttpRequestConnections has a connection / required scopes set up correctly. |
Result output cannot be auto-bridged. | Same activities as above, but emitted when the source identifier is implicit and the bridge cannot run — points the user at building the HttpRequestConnections themselves. |
FindFiles search location. | Tells the user the modern activity does not support "search everywhere"; the migrator defaults the search root to My Drive. |
InsertText.Position = AT_INDEX | Modern activity does not support index-based insert; user must change the position manually. |
SaveOutlookMailMessage.SaveAsType ≠ TextOnly | Same on the Mail extension; the migrator either fails the migration or honours the SaveOutlookMailMessage_IgnoreSaveAsType config flag. |
| Filter migration not supported | Emitted by GetMailMessages-style activities when the classic filter expression cannot be ported. |
SendEmail attachment deduplication | The modern activity does not auto-dedupe attachments; warning only when at least one attachment is set. |
AddDeleteColumns.Name | Column-letter form cannot be auto-converted to ColumnPosition. |
Sheets Rows / Columns | AddNewSheet and CreateNewSpreadsheet cannot reproduce custom dimensions. |
ModifyEvent.InstancesOption ≠ THIS_EVENT | Only THIS_EVENT is supported. |
CreateFilePermission.Result | Modern activity returns AccessUrl instead of a structured permission. |
ConnectionId cannot be inferred | Emitted by UserConfiguredPropertyMigrator when no config-file rule matches. |